fix securestring subsequence returning misplaced characters for a nonzero start index and bounds check its range
What changed, and why it matters
This commit updates a submodule called 'drongo' to fix a bug in a SecureString helper. The bug caused the wrong characters to be returned when extracting a portion of a protected string starting from a nonzero position, and it also added a range check to prevent out-of-bounds access. The actual code change is not visible in the diff because it lives inside the submodule.
Inspect the actual diff inside the drongo submodule at d31b0249542d4616187e01466a81f98f1d70c935 to confirm the fix, add regression tests for SecureString.subSequence with nonzero start indices and boundary values, and verify no other code relied on the previously incorrect behavior.
Security signals we found
SecureString subsequence bug could expose or mis-handle sensitive character data
Missing bounds check could allow out-of-bounds access
Fix is delivered as a submodule bump, hiding the actual code diff
Evidence from the diff
The commit is a submodule bump for ‘drongo’ from 499a656b to d31b0249. The commit message states it fixes SecureString.subSequence(int start, int end) so it returns the correct characters when start > 0, and bounds-checks the requested range. The visible diff only shows the submodule pointer change; the real implementation diff is not included, so we cannot verify the exact fix or confirm whether prior behavior allowed crashes, information leakage, or incorrect cryptographic material handling.
Changed components
drongo submoduleSecureString classInspect captured patch +1 / −1
### drongo
@@ -1 +1 @@
-Subproject commit 499a656b0fb0aaed701aa4d32702a3c32818c813
+Subproject commit d31b0249542d4616187e01466a81f98f1d70c935Why this scored 44/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.