-
-
Notifications
You must be signed in to change notification settings - Fork 151
Closed
Labels
oss-fuzzIssue uncovered by oss-fuzz fuzzerIssue uncovered by oss-fuzz fuzzeryamlIssue related to YAML format backendIssue related to YAML format backend
Milestone
Description
(note: issue found by OSS-Fuzz: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=50431)
Looks like there is an uncaught IllegalArgumentException
for certain input; problem caught by Fuzzing.
Stack trace looks like
== Java Exception: java.lang.IllegalArgumentException: Not a valid Unicode code point: 0xE30EEE
at java.base/java.lang.Character.toChars(Character.java:9175)
at org.yaml.snakeyaml.scanner.ScannerImpl.scanFlowScalarNonSpaces(ScannerImpl.java:1973)
at org.yaml.snakeyaml.scanner.ScannerImpl.scanFlowScalar(ScannerImpl.java:1919)
at org.yaml.snakeyaml.scanner.ScannerImpl.fetchFlowScalar(ScannerImpl.java:1068)
at org.yaml.snakeyaml.scanner.ScannerImpl.fetchDouble(ScannerImpl.java:1050)
at org.yaml.snakeyaml.scanner.ScannerImpl.fetchMoreTokens(ScannerImpl.java:436)
at org.yaml.snakeyaml.scanner.ScannerImpl.checkToken(ScannerImpl.java:251)
at org.yaml.snakeyaml.parser.ParserImpl$ParseImplicitDocumentStart.produce(ParserImpl.java:214)
at org.yaml.snakeyaml.parser.ParserImpl.peekEvent(ParserImpl.java:166)
at org.yaml.snakeyaml.parser.ParserImpl.getEvent(ParserImpl.java:176)
at com.fasterxml.jackson.dataformat.yaml.YAMLParser.nextToken(YAMLParser.java:403)
I think SnakeYAML should catch the problem, re-throw -- content is invalid, but should not get through as IAE.
I created #401 for the test.
Metadata
Metadata
Assignees
Labels
oss-fuzzIssue uncovered by oss-fuzz fuzzerIssue uncovered by oss-fuzz fuzzeryamlIssue related to YAML format backendIssue related to YAML format backend