Server crash via oversized print request
Published Sep 12, 2023 · Updated Sep 26, 2024
Buffer overflow in CBM Control de Ciber 1.650 allows remote attackers to crash its server via a crafted print request. The printing function processes an oversized attacker-controlled field without an effective length bound, overflowing its destination buffer. The request is unauthenticated, but the overflow is triggered only when an administrator accepts or deletes the queued print request.
Summary
What happened
Buffer overflow in CBM Control de Ciber 1.650 allows remote attackers to crash its server via a crafted print request. The printing function processes an oversized attacker-controlled field without an effective length bound, overflowing its destination buffer. The request is unauthenticated, but the overflow is triggered only when an administrator accepts or deletes the queued print request.
The record
- CVE
- CVE-2022-48475
- Published
- Sep 12, 2023
- Updated
- Sep 26, 2024
- Vendor
- CBM
- Product
- Control de Ciber
- Classifications
- CWE-120, CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 12, 2023CVE publishedPublication date reported by the CVE source.
- Sep 26, 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=v1.650
What conditions does exploitation require?
What is affected?
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
- CVE-2022-48475 Print buffer-overflow proof of conceptproof of concept · demonstrated
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