Possible out of range input buffer access about cpp-base64

[cyb70289]

"a" isn't valid base64 string to decode.

Indeed. But IMO invalid input should not cause undefined behaviour to a lib.

[ReneNyffenegger]

I've replaced encoded_string[] with encoded_string.at() in decode() (38c6315)

[Satancito]

"a" isn't valid base64 string to decode.

[pke]

I have to agree with @cyb70289 here. A lib should never trust user input. It should validate everything and all the time. If "a" isn't a valid base64 string to decode then the lib has to properly throw and not just crash (and introduce potential security risks by doing this).

The test suite for this lib would have to be brought up to another level to reveal all those security flaws properly. Starting by adding a regression test for this bug. Irrc the google-test library could also detect invalid memory access, but I would have to check the docs again.

[BullyWiiPlaza]

Agreed, why not replace *all* direct array accesses with calls to at(): Saying this is "slow" is really counter-productive and hides severe bugs such as out of bounds accesses that should not go unnoticed. Also, modern compilers might remove redundant bounds checks anyway. In literally every other language these types of bugs would throw an exception but in C/C++ we prefer to be oblivious? I hope this change will be applied at least @ReneNyffenegger