CVE-2005-0109
No exploitation reported by the sources we read.
- Published2005-03-05
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
Hyper-Threading technology, as used in FreeBSD and other operating systems that are run on Intel Pentium and other processors, allows local users to use a malicious thread to create covert channels, monitor the execution of other threads, and obtain sensitive information such as cryptographic keys, via a timing attack on memory cache misses.
Timeline
dates in UTC- 2005-03-0505:00CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2005-0109?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2005-0109?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.1 | = 1.1.5.1 | no fix published | NVD |
| 2.0 | = 2.0 | no fix published | NVD |
| 2.0 | = 2.0.5 | no fix published | NVD |
| 2.1 | = 2.1.0 | no fix published | NVD |
| 2.1 | = 2.1.5 | no fix published | NVD |
| 2.1 | = 2.1.6 | no fix published | NVD |
| 2.1 | = 2.1.6.1 | no fix published | NVD |
| 2.1 | = 2.1.7.1 | no fix published | NVD |
| 2.2 | = 2.2 | no fix published | NVD |
| 2.2 | = 2.2.2 | no fix published | NVD |
| 2.2 | = 2.2.3 | no fix published | NVD |
| 2.2 | = 2.2.4 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 7.0 | = 7.0 | no fix published | NVD |
| 8.0 | = 8.0 | no fix published | NVD |
| 9.0 | = 9.0 | no fix published | NVD |
| 10.0 | = 10.0 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2.1 | = 2.1 | no fix published | NVD |
| 3.0 | = 3.0 | no fix published | NVD |
| 4.0 | = 4.0 | no fix published | NVD |
5 more products in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
Advisories and patches
- securitytracker.comPatch · Vendor Advisory
- sunsolve.sun.comVendor Advisory
- www.securityfocus.comPatch · Vendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.05.6read 2026-10-23
- NVDCVSS 2.04.7read 2026-10-23
- FIRST EPSSEPSS score0.5 %2026-10-22
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N
- Published
- 2005-03-05
- Last Modified
- 2026-06-16
- NVD status
- Modified
Frequently asked questions
What is CVE-2005-0109?
Is CVE-2005-0109 actively exploited?
What is the CVSS score for CVE-2005-0109?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.