Bug 1216624 (CVE-2023-45960) - VUL-0: CVE-2023-45960: dom4j: sensitive information leak via the setFeature function
Summary: VUL-0: CVE-2023-45960: dom4j: sensitive information leak via the setFeature f...
Status: RESOLVED INVALID
Alias: CVE-2023-45960
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/382964/
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-10-26 15:12 UTC by SMASH SMASH
Modified: 2023-10-30 08:47 UTC (History)
1 user (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 SMASH SMASH 2023-10-26 15:12:04 UTC 
An issue in dom4.j org.dom4.io.SAXReader v.2.1.4 and before allows a remote attacker to obtain sensitive information via the setFeature function.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45960
Comment 2 Gabriele Sonnu 2023-10-30 08:47:16 UTC 
Quoting from the upstream issue [0]:

> No, dom4j is not affected by that. More precisely, CVE-2023-45960 is not a
> vulnerability. The setFeature method sets the features of the XML parser in
> use - in fact, it just invokes the setFeature method of the underlying SAX
> parser. Different features of the XML parser can be safe in one case and
> unsafe in another - that's how it works in the world.

Closing this.

[0] https://github.com/dom4j/dom4j/issues/171