CVE-2004-1901
published 2004-12-31CVE-2004-1901: Portage before 2.0.50-r3 allows local users to overwrite arbitrary files via a hard link attack on the lockfiles.
PriorityP412medium5.5CVSS 3.1
AVLACLPRLUINSUCNIHAN
EPSS
0.37%
28.4th percentile
Portage before 2.0.50-r3 allows local users to overwrite arbitrary files via a hard link attack on the lockfiles.
Affected
3 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| gentoo | linux | — | — |
| gentoo | portage | < 2.0.50 | 2.0.50 |
| gentoo | portage | — | — |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
nvdv2.04.6MEDIUMAV:L/AC:L/Au:N/C:P/I:P/A:P
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
CWE
Improper Link Resolution Before File Access ('Link Following')
mitre_cwe
CWE-59 Improper Link Resolution Before File Access ('Link Following')
CWE-59: Improper Link Resolution Before File Access ('Link Following')
The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.
Background: Soft links are a UNIX term that is synonymous with simple shortcuts on Windows-based platforms.
Modes of Introduction:
Phase: Implementation
Note: REALIZATION: This weakness is caused during implementation of an architectural security tactic.
Common Consequences:
Scope: Confidentiality, Integrity, Access Control. Impact: Read Files or Directories, Modify Files or Directories, Bypass Protection Mechanism. An attacker may be able to traverse the file system to unintended locations and read or overwrite the contents of unexpe
CWE
UNIX Hard Link
mitre_cwe·CVSS 5.5
[MEDIUM] CWE-62 UNIX Hard Link
CWE-62: UNIX Hard Link
The product, when opening a file or directory, does not sufficiently account for when the name is associated with a hard link to a target that is outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.
Failure for a system to check for hard links can result in vulnerability to different types of attacks. For example, an attacker can escalate their privileges if a file used by a privileged program is replaced with a hard link to a sensitive file (e.g. /etc/passwd). When the process opens the file, the attacker can assume the privileges of that process.
Modes of Introduction:
Phase: Implementation
Common Consequences:
Scope: Confidentiality, Integrity. Impact: Read Files or Directories, Modify File
http://secunia.com/advisories/11305http://security.gentoo.org/glsa/glsa-200404-01.xmlhttp://www.securityfocus.com/bid/10060https://exchange.xforce.ibmcloud.com/vulnerabilities/15754http://secunia.com/advisories/11305http://security.gentoo.org/glsa/glsa-200404-01.xmlhttp://www.securityfocus.com/bid/10060https://exchange.xforce.ibmcloud.com/vulnerabilities/15754
2004-12-31
Published