CVE-2010-0118 json
Bournal before 1.4.1 allows local users to overwrite arbitrary files via a symlink attack on unspecified temporary files associated with a…
published 2010-02-25 16 y ago modified 2026-06-16 4 mo ago also EUVD-2010-0150
- cvss
- 3.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 25%
- public exploits
- 0
- none known
Summary
Bournal before 1.4.1 allows local users to overwrite arbitrary files via a symlink attack on unspecified temporary files associated with a --hack_the_gibson update check.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2010-0118 updated
bournal: updated version 1.4.1 fixes two vulnerabilities
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.33% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 3.3 | AV:L/AC:M/Au:N/C:N/I:P/A:P |
Classification
- Weakness
-
- CWE-59 Improper Link Resolution Before File Access
References
-
lists.fedoraproject.org
/pipermail/package-announce/2010-March/036701.html
vendor-advisory
-
lists.fedoraproject.org
/pipermail/package-announce/2010-March/036764.html
vendor-advisory
-
lists.fedoraproject.org
/pipermail/package-announce/2010-March/036697.html
vendor-advisory
-
secunia.com
/advisories/38554
third-party-advisory, vendor-advisory
-
secunia.com
/secunia_research/2010-6/
vendor-advisory
-
securityfocus.com
/archive/1/509685/100/0/threaded
mailing-list
-
secunia.com
/advisories/38814
third-party-advisory
-
securityfocus.com
/bid/38353
vdb-entry
Sources
- CVE List CVE-2010-0118
- NVD CVE-2010-0118
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.