Code execution via wp6sr.dll stack buffer overflow
Published Jan 25, 2024 · Updated Oct 18, 2024
Stack buffer overflow in Symantec Data Loss Prevention 12.0 through 14.0.2 allows remote attackers to execute code via a crafted document. The flaw resides in wp6sr.dll, but the public disclosure does not identify the document parser or the unchecked operation that overruns its stack buffer. Exploitation requires a user on an affected Windows system to open the attacker-supplied document, after which code executes in the vulnerable process.
Summary
What happened
Stack buffer overflow in Symantec Data Loss Prevention 12.0 through 14.0.2 allows remote attackers to execute code via a crafted document. The flaw resides in wp6sr.dll, but the public disclosure does not identify the document parser or the unchecked operation that overruns its stack buffer. Exploitation requires a user on an affected Windows system to open the attacker-supplied document, after which code executes in the vulnerable process.
The record
- CVE
- CVE-2024-23617
- Published
- Jan 25, 2024
- Updated
- Oct 18, 2024
- Vendor
- Brocade Communications Systems
- Product
- Symantec Data Loss Prevention
- Classifications
- CWE-120, CWE-119, T1204.002, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 25, 2024CVE publishedPublication date reported by the CVE source.
- Oct 18, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=12.0 <=14.0.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo