Raw vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:NSummary
CVE-2024-22261 is a low-severity Authorization Bypass Through User-Controlled SQL Primary Key (CWE-566) vulnerability in Linuxfoundation Harbor. Its CVSS base score is 2.7 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 35th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-24 (Access Control Decisions) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-2184
Vulnerability Data
SQL-Injection in Harbor allows priviledge users to leak the task IDs
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V6.2.5
Mitigating Controls (NIST 800-53 r5) AI
AC-3 requires enforcement of authorizations on every access request, which directly stops a caller from reaching unauthorized rows via a supplied primary key.
AC-24 mandates that access-control decisions be applied to each request, preventing blind trust of a user-supplied primary key.
Developer testing and evaluation can discover SQLi flaws before deployment but does not stop their introduction.
Input validation directly stops untrusted data from reaching SQL query construction without neutralization.
Least privilege reduces the set of records an account can touch, limiting blast radius even if the key check is missing.
Secure engineering principles require parameterized queries and input sanitization that structurally eliminate SQLi.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Enforcing policy-based authorization and least privilege directly prevents actor-controlled primary-key access to unauthorized records.
Secure SDLC practices include input validation, parameterized queries, and authorization checks that eliminate this class of SQL primary-key bypass.
Training raises developer awareness of SQLi risks and can reduce introduction likelihood (partial) but removes none of the actual coding flaw's risk by itself since technical neutralization is still required.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect missing authorization checks and unsafe SQL construction before release.
Enforcing information-access restrictions prevents direct use of user-supplied primary keys to bypass authorization checks.
Access-control policy sets the governance expectation that all data access must be authorized, indirectly supporting prevention of CWE-566.
Early warnings and shared best-practice information help organizations apply the latest remediation techniques against SQL-injection vulnerabilities.
Threat-intelligence feeds that surface new SQL-injection campaigns enable rapid updates to query-construction defenses and detection signatures before exploitation occurs.
Secure-coding rules and security testing phases mandate the use of parameterized queries or equivalent escaping, preventing the construction of dynamic SQL statements from untrusted input.