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
F15424279: D11323.id27209.diff
Sat, Mar 22, 9:15 PM
F15422559: D11323.id27194.diff
Sat, Mar 22, 9:21 AM
F15413472: D11323.id27194.diff
Wed, Mar 19, 7:01 PM
F15401442: D11323.diff
Mon, Mar 17, 5:45 PM
F15395851: D11323.diff
Sun, Mar 16, 10:09 AM
F15389751: D11323.id27194.diff
Sat, Mar 15, 5:37 AM
F15388948: D11323.id.diff
Sat, Mar 15, 4:43 AM
F15386311: D11323.id.diff
Sat, Mar 15, 12:20 AM
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.