Bug 1226352 - VUL-0: CVE-2024-35328: python-ruamel.yaml: libyaml: denial of service in yaml_parser_parse of the file /src/libyaml/src/parser.c.
Summary: VUL-0: CVE-2024-35328: python-ruamel.yaml: libyaml: denial of service in yaml...
Status: IN_PROGRESS
Alias: None
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents (show other bugs)
Version: unspecified
Hardware: Other Other
: P3 - Medium : Normal
Target Milestone: ---
Assignee: Security Team bot
QA Contact: Security Team bot
URL: https://smash.suse.de/issue/410659/
Whiteboard:
Keywords:
Depends on:
Blocks: CVE-2024-35328
  Show dependency tree / graph
 
Reported: 2024-06-14 14:04 UTC by Camila Camargo de Matos
Modified: 2024-07-01 06:40 UTC (History)
4 users (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Camila Camargo de Matos 2024-06-14 14:04:04 UTC 
+++ This bug was initially created as a clone of Bug #1226341 +++

libyaml v0.2.5 is vulnerable to DDOS. Affected by this issue is the function yaml_parser_parse of the file /src/libyaml/src/parser.c.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-35328
https://www.cve.org/CVERecord?id=CVE-2024-35328
https://github.com/idhyt/pocs/blob/main/libyaml/CVE-2024-35328.c
https://bugzilla.redhat.com/show_bug.cgi?id=2292339
Comment 1 Camila Camargo de Matos 2024-06-14 17:11:30 UTC 
See bug #1226341 for a reference link which is the upstream GitHub issue where this possible vulnerability is being discussed.
Comment 3 Daniel Garcia 2024-06-18 11:31:49 UTC 
Possibly not a bug, upstream discussion can be found here:
https://github.com/yaml/libyaml/issues/298
Comment 4 Daniel Garcia 2024-06-26 09:55:28 UTC 
The code snippet uses the API in a wrong way, calling yaml_parser_pars without initializing the parser with yaml_parser_initialize. The correct usage is documented here: https://pyyaml.org/wiki/LibYAML

I've reviewed the embed code in the package and is not affected at all because it is using the API in the correct way. The parsere class initializes the internal yaml parser in the constructor before any usage