Process crash via malformed PCX image
Published Jan 14, 2025 · Updated Jan 15, 2025
Improper input validation in the PCX codec in BlackBerry QNX SDP 8.0, 7.1, and 7.0 allows remote attackers to crash a consuming process. BlackBerry identifies the PCX codec as the locus but has not disclosed which image field is improperly validated or the resulting invalid operation. The process must decode attacker-supplied PCX data; impact is limited to interruption of that process, with no reported code execution or data access.
Summary
What happened
Improper input validation in the PCX codec in BlackBerry QNX SDP 8.0, 7.1, and 7.0 allows remote attackers to crash a consuming process. BlackBerry identifies the PCX codec as the locus but has not disclosed which image field is improperly validated or the resulting invalid operation. The process must decode attacker-supplied PCX data; impact is limited to interruption of that process, with no reported code execution or data access.
The record
- CVE
- CVE-2024-48858
- Published
- Jan 14, 2025
- Updated
- Jan 15, 2025
- Vendor
- BlackBerry
- Product
- QNX Software Development Platform
- Classifications
- CWE-1287, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 14, 2025CVE publishedPublication date reported by the CVE source.
- Jan 15, 2025Record 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=8.0, 7.1 and 7.0
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