Page MenuHomePhabricator

Fix a possible segfault when parsing JSON containing very large strings
ClosedPublic

Authored by joshuaspence on Jan 11 2015, 10:29 AM.
Tags
None
Referenced Files
F18086482: D11323.diff
Tue, Aug 5, 10:07 PM
F17884009: D11323.id27209.diff
Mon, Jul 28, 11:42 PM
F17837909: D11323.id.diff
Sat, Jul 26, 5:55 PM
Unknown Object (File)
Jul 7 2025, 6:03 PM
Unknown Object (File)
Jun 27 2025, 2:37 AM
Unknown Object (File)
Jun 7 2025, 3:43 PM
Unknown Object (File)
Apr 27 2025, 1:16 AM
Unknown Object (File)
Apr 19 2025, 12:27 PM
Subscribers

Diff Detail

Repository
rPHU libphutil
Branch
master
Lint
Lint Errors
SeverityLocationCodeMessage
Errorsrc/parser/__tests__/json/base64.data:1TXT4File Does Not End in Newline
Warningsrc/parser/__tests__/json/base64.data:1TXT3Line Too Long
Warningsrc/parser/__tests__/json/base64.json:1TXT3Line Too Long
Unit
Tests Passed
Build Status
Buildable 3752
Build 3763: [Placeholder Plan] Wait for 30 Seconds

Event Timeline

joshuaspence retitled this revision from to Fix a possible segfault when parsing JSON containing very large strings.
joshuaspence updated this object.
joshuaspence edited the test plan for this revision. (Show Details)
joshuaspence added a reviewer: epriestley.
epriestley edited edge metadata.

I think that even with (?:...) we can blow the stack -- see phutil_is_utf8_slowly() -- but the limits are high enough to be reasonable.

This revision is now accepted and ready to land.Jan 11 2015, 5:01 PM
This revision was automatically updated to reflect the committed changes.