Unspecified impact via non-string mode type confusion
Published Feb 19, 2020 · Updated Aug 6, 2024
Type confusion in HHVM before 3.9.5, 3.10.0 through 3.12.3, and 3.13.0 through 3.14.1 allows attackers to cause unspecified impact. The native mcrypt extension accepts the mcrypt_get_block_size mode argument as a Variant and calls asCStrRef on it without first enforcing a string type. Reachability depends on application code passing an attacker-controlled non-string value; the public records do not specify a concrete confidentiality, integrity, or availability consequence.
Summary
What happened
Type confusion in HHVM before 3.9.5, 3.10.0 through 3.12.3, and 3.13.0 through 3.14.1 allows attackers to cause unspecified impact. The native mcrypt extension accepts the mcrypt_get_block_size mode argument as a Variant and calls asCStrRef on it without first enforcing a string type. Reachability depends on application code passing an attacker-controlled non-string value; the public records do not specify a concrete confidentiality, integrity, or availability consequence.
The record
- CVE
- CVE-2016-1000005
- Published
- Feb 19, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-843
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 19, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 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