Privilege escalation and service interruption via buffer overflow
Published Sep 15, 2023 · Updated Sep 25, 2024
Buffer overflow in OPSWAT MetaDefender Kiosk before 4.6.2 allows physically proximate attackers to interrupt service and escalate privileges. The product fails to reject an overly long input before processing it, causing a buffer overflow; OPSWAT has not disclosed the affected field or routine. Physical access and user interaction are required, and exploitation can sever Kiosk communications or elevate privileges.
Summary
What happened
Buffer overflow in OPSWAT MetaDefender Kiosk before 4.6.2 allows physically proximate attackers to interrupt service and escalate privileges. The product fails to reject an overly long input before processing it, causing a buffer overflow; OPSWAT has not disclosed the affected field or routine. Physical access and user interaction are required, and exploitation can sever Kiosk communications or elevate privileges.
The record
- CVE
- CVE-2023-36659
- Published
- Sep 15, 2023
- Updated
- Sep 25, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, CWE-119, T1499.004
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 15, 2023CVE publishedPublication date reported by the CVE source.
- Sep 25, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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