CVE-2016-1493 json
Intel Driver Update Utility before 2.4 retrieves driver updates in cleartext, which makes it easier for man-in-the-middle attackers to exec…
published 2016-01-29 10 y ago modified 2026-06-17 4 mo ago also EUVD-2016-2592
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 69%
- public exploits
- 0
- none known
Summary
Intel Driver Update Utility before 2.4 retrieves driver updates in cleartext, which makes it easier for man-in-the-middle attackers to execute arbitrary code via a crafted file.
Patch / fix
Exploit prediction
1.25% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.6 | AV:N/AC:H/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-345 Insufficient Verification of Data Authenticity
References
-
security-center.intel.com
/advisory.aspx?intelid=INTEL-SA-00048&languageid=en-fr
patch, vendor-advisory
- packetstormsecurity.com /files/135314/Intel-Driver-Update-Utility-2.2.0.5-Man-In-The-Middle.html
- coresecurity.com /advisories/intel-driver-update-utility-mitm
-
securityfocus.com
/archive/1/537327/100/0/threaded
mailing-list
-
seclists.org
/fulldisclosure/2016/Jan/56
mailing-list
Sources
- CVE List CVE-2016-1493
- NVD CVE-2016-1493
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.