Unauthenticated code execution via unchecked register length
Published Mar 13, 2020 · Updated Aug 4, 2024
Stack-based buffer overflow in Xerox Phaser 3320 firmware 53.006.16.000 allows remote attackers to execute arbitrary code without authentication. The Google Cloud Print registration handler passes an unchecked action-value length to memcpy(), overflowing a local stack buffer. A crafted register request reaches the network-exposed implementation with no credentials or user interaction and grants code execution on the printer.
Summary
What happened
Stack-based buffer overflow in Xerox Phaser 3320 firmware 53.006.16.000 allows remote attackers to execute arbitrary code without authentication. The Google Cloud Print registration handler passes an unchecked action-value length to memcpy(), overflowing a local stack buffer. A crafted register request reaches the network-exposed implementation with no credentials or user interaction and grants code execution on the printer.
The record
- CVE
- CVE-2019-13171
- Published
- Mar 13, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 13, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.
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