-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integer overflow in the GenericReader::ParseNumber()
function of include/rapidjson/reader.h
when parsing JSON text from a stream.
#2303
Comments
Hello all, |
Can you demonstrate this issue? If rapidjson::Document is parsed from some file with a large number (via IStreamWrapper isw(ifs); Document d; d.ParseStream(isw); ), any integer value within the acceptable value range of uint64_t or int64_t, the parser will parse correctly and show the type with GetType() and IsInt64()/IsUInt64(). If an integer value exceeding these range limits is passed to the parser, the parser treats it as the type double and does some rounding if the integer value doesn't have a fully accurate double representation. If the numeric value, be it integer or a decimal, exceeds the limits of double then the parser will report the error ParseErrorCode::kParseErrorNumberTooBig. I don't see where is the integer overflow that CVE-2024-39684 has reported in GenericReader::ParseNumber. |
Hello, Based on the original Microsoft report, they use GitHub CNA to communicate CVE details to maintainers: |
Hey, I would just like to clarify - I believe the original link from NIST is misguiding. This seems to be an issue with the Microsoft team who manages
|
The integer overflow issue appears to reported in https://nvd.nist.gov/vuln/detail/CVE-2024-39684
Any fix for this issue provided in the current version 1.1.0?
The text was updated successfully, but these errors were encountered: