fix(NODE-3021): fix a long standing bug in Decimal128.fromString() #458
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tzhuan
changed the title
dariakp
added
the
tracked-in-jira
dariakp
requested changes
Sep 8, 2021
nbbeeken
approved these changes
Sep 8, 2021
Co-authored-by: Daria Pardue <[email protected]>
dariakp
approved these changes
Sep 9, 2021
|
Thank you! Hope that you can make a new bson npm release (and also a new mongodb node driver npm release) as soon as possible because this bug is potentially a significant vulnerability especially for financial usages. |
|
@tzhuan Yes, we are definitely planning to do a release soon. Thank you again! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fix a long standing bug in
Decimal128.fromString()What changed?
The
representationstring was wrongly used to find the significant digits. Thedigitsarray should be used instead.Note that the v2.0 and v3.0 branches also have this bug.