dbcve.org
HarborApplication · Linuxfoundation

CVE-2024-22261

MEDIUM · 5.5 CVSS v3.1 Published 2024-06-11
Fix available
A fix is available. Upgrade to 2.8.6 / 2.9.4 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
SQL-Injection in Harbor allows priviledge users to leak the task IDs

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

SQL injection vulnerability in Harbor allows authenticated privileged users to manipulate database queries and leak internal task IDs. The vulnerability exists in a component handling task data without proper input sanitization or parameterized queries.

MitigationApply vendor-provided patch for CVE-2024-22261. As immediate mitigation, restrict Harbor administrative access to trusted personnel only until patch can be deployed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
HarborApplication
Affected:>= 2.8.1, < 2.8.6>= 2.9.0, < 2.9.4>= 2.10.0, < 2.10.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine Harbor installed version
    Call the Harbor API endpoint /api/v2.0/systeminfo/get or check the Harbor UI footer which displays the version number. Alternatively, check the harbor.yml configuration file or docker container labels if running in containers.
    Affected if The installed version falls within these ranges: >= 2.8.1 and < 2.8.6; >= 2.9.0 and < 2.9.4; >= 2.10.0 and < 2.10.2
  2. Confirm Harbor is running and accessible
    Verify the Harbor web interface or API is accessible on the configured host and port (default 443 for HTTPS). Use curl or a browser to confirm the service responds.
    Affected if Harbor is exposed and running any vulnerable version from step 1
  3. Identify privileged user accounts
    Log into Harbor as an administrator and review the Users section in the UI, or query the /api/v2.0/users API endpoint to list all user accounts. Note which users have administrator privileges.
    Affected if Any privileged (administrator) Harbor user accounts exist in the system
  4. Check for task-related API activity
    Review Harbor logs or API access logs for requests to task-related endpoints such as /api/v2.0/tasks or /api/v2.0/jobs. These endpoints handle the task data component where the SQL injection exists.
    Affected if The task API endpoints are accessible and being used in any vulnerable version from step 1

You are affected if your Harbor installation version is 2.8.1 through 2.8.5, 2.9.0 through 2.9.3, or 2.10.0 through 2.10.1, and the system is running with privileged user accounts able to access task-related API endpoints.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.8.6 / 2.9.4 / 2.10.2 or later
Fixed in 2.8.62.9.42.10.2
Interim mitigation

Apply vendor-provided patch for CVE-2024-22261. As immediate mitigation, restrict Harbor administrative access to trusted personnel only until patch can be deployed.

Recommended fix High confidence

Upgrade to Harbor 2.8.6, 2.9.4, 2.10.2 or later (prefer latest stable release in your minor version branch)

  1. Backup your existing Harbor data and configuration (including database, registry storage, and harbor.yml config)
  2. Download the fixed Harbor release (2.8.6, 2.9.4, or 2.10.2 or later) from the official Harbor releases
  3. Stop all Harbor services using 'docker-compose down' or the equivalent for your deployment
  4. Extract the new Harbor package and update your configuration as needed (harbor.yml)
  5. Run the Harbor install/upgrade script (install.sh or prepare script)
  6. Start Harbor services using 'docker-compose up -d'
  7. Verify the upgrade was successful by checking the Harbor UI and API
Caveat Review Harbor release notes for any breaking changes between your current and target version, particularly regarding database migrations and API compatibility

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Harbor Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-22261 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-22261 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data