Home
» Security vulnerabilities
» CVE-2004-1901
Portage before 2.0.50-r3 allows local users to overwrite arbitrary files via a hard link attack on the lockfiles.
NVD Status： Modified ，CVE State: published
Threat Intelligence & Risk Assessment for CVE-2004-1901
Conclusion & alert: CVE-2004-1901 is rated Low Risk (32.2/100) : CVSS Medium severity, with low exploitation likelihood (EPSS 0.37%).Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.
Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.
Exploit prediction scoring system (EPSS) score for CVE-2004-1901
EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).
#
Date
Old EPSS score
New EPSS score
Delta (New - Old)
1
2026-06-15
0.05%
0.37%
+0.31%
2
2025-03-17
0.04%
0.05%
+0.01%
3
2023-03-07
—
0.04%
—
Full EPSS history
(4 records total)
Common vulnerability scoring system (CVSS) metrics for CVE-2004-1901
CVSS metrics for this CVE.
Base score
Version
Severity
Vector
Exploitability
Impact
Score source
5.5
3.1
MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
1.8
3.6
[email protected]
5.5
3.1
MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
1.8
3.6
134c704f-9b21-4f2e-91b3-4a467353bcc0
4.6
2.0
MEDIUM
AV:L/AC:L/Au:N/C:P/I:P/A:P
Click to expand
Access vector (AV:L)
Requires local access to the target system.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
3.9
6.4
[email protected]
Weakness enumeration for CVE-2004-1901
Affected software / configurations for CVE-2004-1901
Vendor
Product
Version
Raw CPE
gentoo
portage
< 2.0.50
cpe:2.3:a:gentoo:portage:*:*:*:*:*:*:*:*
gentoo
portage
2.0.50
cpe:2.3:a:gentoo:portage:2.0.50:-:*:*:*:*:*:*
gentoo
linux
1.4
cpe:2.3:o:gentoo:linux:1.4:-:*:*:*:*:*:*
gentoo
linux
1.4
cpe:2.3:o:gentoo:linux:1.4:rc1:*:*:*:*:*:*
gentoo
linux
1.4
cpe:2.3:o:gentoo:linux:1.4:rc2:*:*:*:*:*:*
References for CVE-2004-1901
cvelogic
Threat Intelligence