The changelog command in Apt before 1.0.9.2 allows local users to write to arbitrary files via a symlink attack on the changelog file.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for help- Published
- Oct 15, 2014
- Updated
- Jun 16, 2026
- EPSS
- 0.4% · 30th percentile
- CWE
- CWE-59
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
14
Monitor
Low priority for now.
- CVSS
- 14 / 40 · 3.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| debian | advanced package tool | cpe:2.3:a:debian:advanced_package_tool |
| debian | apt | cpe:2.3:a:debian:apt |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian advanced package toolup to 1.0.9.1 inclusive
- debian advanced package tool1.0.8
- debian apt0.9.7.9
- debian apt1.0.9
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | apt | before 1.0.9.2 | 1.0.9.2 |
| Debian:7 | apt | before 0.9.7.9+deb7u6 | 0.9.7.9+deb7u6 |
Same product
debian: all recordsOther highest-scoring records for the same primary product.
- CVE-2009-1358apt-get in apt before 0.7.21 does not check for the correct error code from gpgv, which causes apt to treat a repository as valid even when 41Plan
- CVE-2009-1300apt 0.7.20 does not check when the date command returns an "invalid date" error, which can prevent apt from loading security updates in time41Plan
- CVE-2019-3462Incorrect sanitation of the 302 redirect field in HTTP transport method of apt versions 1.4.8 and earlier can lead to content injection by a36Monitor
- CVE-2014-0490The apt-get download command in APT before 1.0.9 does not properly validate signatures for packages, which allows remote attackers to execut31Monitor
- CVE-2014-0489APT before 1.0.9, when the Acquire::GzipIndexes option is enabled, does not validate checksums, which allows remote attackers to execute arb31Monitor
- CVE-2014-0487APT before 1.0.9 does not verify downloaded files if they have been modified as indicated using the If-Modified-Since header, which has unsp31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:apt | 1.0.9.2 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- P · data or configuration can be modified
- Availability
- P · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- None
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
CWE-59 · Improper Link Resolution Before File Access ('Link Following')CVSS vector
AV:L/AC:L/Au:N/C:N/I:P/A:P
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
- Obfuscated Files or Information: HTML SmugglingT1027.006
- Obfuscated Files or Information: Embedded PayloadsT1027.009
- Boot or Logon Autostart Execution:Shortcut ModificationT1547.009
- Hide Artifacts: Resource ForkingT1564.009
- Hijack Execution Flow: Executable Installer File Permissions WeaknessT1574.005
- Hijack Execution Flow: Services File Permissions WeaknessT1574.010
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- secunia.com/advisories/61158
- secunia.com/advisories/61333
- secunia.com/advisories/61768
- www.debian.org/security/2014/dsa-3048
- www.securityfocus.com/bid/70310
- www.ubuntu.com/usn/USN-2370-1
- bugs.debian.org/cgi-bin/bugreport.cgi?bug=763780
- exchange.xforce.ibmcloud.com/vulnerabilities/96951
Vendor advisories and official records. Exploit/PoC links are deliberately left out.