Home
» Security vulnerabilities
» CVE-2024-22261
SQL-Injection in Harbor allows priviledge users to leak the task IDs
NVD Status： Analyzed ，CVE State: published
Threat Intelligence & Risk Assessment for CVE-2024-22261
Conclusion & alert: CVE-2024-22261 is rated Low Risk (33.4/100) : CVSS Low severity, with medium exploitation likelihood (EPSS 0.47%).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-2024-22261
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-02
0.59%
0.47%
-0.12%
2
2026-05-21
0.48%
0.59%
+0.12%
3
2026-05-14
—
0.48%
—
Full EPSS history
(11 records total)
Common vulnerability scoring system (CVSS) metrics for CVE-2024-22261
CVSS metrics for this CVE.
Base score
Version
Severity
Vector
Exploitability
Impact
Score source
2.7
3.1
LOW
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N
Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
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:H)
They need powerful rights—admin, root, or similar—before this pays off.
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:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
1.2
1.4
[email protected]
5.5
3.1
MEDIUM
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N
Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
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:H)
They need powerful rights—admin, root, or similar—before this pays off.
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:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
1.2
4.2
[email protected]
Weakness enumeration for CVE-2024-22261
GitHub Security Advisory for CVE-2024-22261
GHSA-vw63-824v-qf2j · Severity: low · Ecosystem: go
— SQL Injection in Harbor scan log API
Affected software / configurations for CVE-2024-22261
References for CVE-2024-22261
cvelogic
Threat Intelligence