CVE-2016-5080 in the critical feed json
Integer overflow in the rtxMemHeapAlloc function in asn1rt_a.lib in Objective Systems ASN1C for C/C++ before 7.0.2 allows context-dependent…
published 2016-07-19 10 y ago modified 2026-06-17 4 mo ago also EUVD-2016-6033
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 10.1%
- EPSS 10.1% chance of exploitation in 30 days, percentile 95%
- public exploits
- 0
- none known
Summary
Integer overflow in the rtxMemHeapAlloc function in asn1rt_a.lib in Objective Systems ASN1C for C/C++ before 7.0.2 allows context-dependent attackers to execute arbitrary code or cause a denial of service (heap-based buffer overflow), on a system running an application compiled by ASN1C, via crafted ASN.1 data.
Exploit prediction
10.06% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
References
-
tools.cisco.com
/security/center/content/CiscoSecurityAdvisory/cisco-sa-20160721-asn1c
vendor-advisory
- source.android.com /security/bulletin/2017-01-01.html
-
securityfocus.com
/archive/1/538952/100/0/threaded
mailing-list
-
github.com
/programa-stic/security-advisories/tree/master/ObjSys/CVE-2016-5080
technical-description, third-party-advisory
-
kb.cert.org
/vuls/id/790839
third-party-advisory, us-government-resource
-
ncsc.nl
/dienstverlening/response-op-dreigingen-en-incidenten/beveiligingsadviezen/NCSC-2016-0650+1.00+Kwetsbaarheid+v
third-party-advisory
- oracle.com /technetwork/security-advisory/cpuoct2018-4428296.html
-
securitytracker.com
/id/1036386
vdb-entry
- packetstormsecurity.com /files/137970/Objective-Systems-Inc.-ASN1C-For-C-C-Heap-Memory-Corruption.html
-
seclists.org
/fulldisclosure/2016/Jul/65
mailing-list
-
securityfocus.com
/bid/91836
vdb-entry
Sources
- CVE List CVE-2016-5080
- NVD CVE-2016-5080
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.