Local memory corruption via unchecked buffer copy
Published Apr 29, 2020 · Updated Aug 4, 2024
Buffer overflow in Cerner medico 26.00 allows local users to corrupt memory by supplying oversized input to an affected component. The X41 advisory identifies unchecked fixed-buffer copies in slim_proxy, dpscrypt, and mkdict, but does not assign issue 1 to a specific file or function. Local access is the stated gate; network reachability through another system tool is unconfirmed, and successful exploitation grants control of the software.
Summary
What happened
Buffer overflow in Cerner medico 26.00 allows local users to corrupt memory by supplying oversized input to an affected component. The X41 advisory identifies unchecked fixed-buffer copies in slim_proxy, dpscrypt, and mkdict, but does not assign issue 1 to a specific file or function. Local access is the stated gate; network reachability through another system tool is unconfirmed, and successful exploitation grants control of the software.
The record
- CVE
- CVE-2020-11675
- Published
- Apr 29, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 29, 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.
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