CVE-2008-3068 in the critical feed json
Microsoft Crypto API 5.131.2600.2180 through 6.0, as used in Outlook, Windows Live Mail, and Office 2007, performs Certificate Revocation L…
published 2008-07-07 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-3058
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 17.4%
- EPSS 17.4% chance of exploitation in 30 days, percentile 97%
- public exploits
- 0
- none known
Summary
Microsoft Crypto API 5.131.2600.2180 through 6.0, as used in Outlook, Windows Live Mail, and Office 2007, performs Certificate Revocation List (CRL) checks by using an arbitrary URL from a certificate embedded in a (1) S/MIME e-mail message or (2) signed document, which allows remote attackers to obtain reading times and IP addresses of recipients, and port-scan results, via a crafted certificate with an Authority Information Access (AIA) extension.
Exploit prediction
17.40% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
References
- cynops.de /advisories/AKLINK-SA-2008-003.txt
-
securityreason.com
/securityalert/3978
third-party-advisory
-
securityfocus.com
/archive/1/494101/100/0/threaded
mailing-list
-
securityfocus.com
/bid/28548
vdb-entry
- klink.name /security/aklink-sa-2008-004-office2007-signatures.txt
- cynops.de /advisories/AKLINK-SA-2008-002.txt
- cynops.de /advisories/AKLINK-SA-2008-004.txt
-
securitytracker.com
/id?1019736
vdb-entry
-
securitytracker.com
/id?1019738
vdb-entry
- klink.name /security/aklink-sa-2008-003-live-mail-smime.txt
- klink.name /security/aklink-sa-2008-002-outlook-smime.txt
-
securitytracker.com
/id?1019737
vdb-entry
- cynops.de /techzone/http_over_x509.html
-
securityfocus.com
/archive/1/493947/100/0/threaded
mailing-list
Sources
- CVE List CVE-2008-3068
- NVD CVE-2008-3068
Fencer Vulns 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.