CVE-2024-22244
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 · uneditedOpen Redirect in Harbor <=v2.8.4, <=v2.9.2, and <=v2.10.0 may redirect a user to a malicious site.
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 confidenceOpen redirect vulnerability in Harbor container registry allows attackers to craft malicious URLs that redirect users to external phishing or malware sites. This occurs due to improper validation of redirect parameters in the web interface, enabling credential theft or malicious content delivery.
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>= 2.8.0, < 2.8.5>= 2.9.0, < 2.9.3= 2.10.0CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Harbor versionRun `harbor -v` or check the Harbor Helm chart/operator version, or inspect the container image tagAffected if version is 2.8.0-2.8.4, 2.9.0-2.9.2, or exactly 2.10.0
-
Verify Harbor web interface is accessibleConfirm Harbor UI is exposed by checking the service/ingress configuration with `kubectl get ingress` or `kubectl get svc` if Harbor is kubernetes-deployedAffected if the web interface is externally accessible or exposed to untrusted networks
-
Check for proxy or WAF URL validation rulesInspect your reverse proxy (nginx, traefik) or WAF configuration for any redirect destination validation rules that block external URLsAffected if no URL validation exists at the proxy layer and Harbor is vulnerable based on version
A user is affected if their Harbor installation version falls within the vulnerable range and the web interface is accessible, without compensating URL validation controls at a proxy or WAF layer.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.8.52.9.3
Upgrade Harbor to versions newer than v2.8.4, v2.9.2, and v2.10.0 to obtain the security patch. If immediate upgrade is not possible, implement URL validation at any proxy or WAF layer to reject external redirect destinations.
Upgrade to Harbor 2.8.5+, 2.9.3+, or 2.10.1+ (latest stable release recommended)
- Identify your current Harbor version using `harbor --version` or checking the Harbor UI footer
- Determine which version branch you are on (2.8.x, 2.9.x, or 2.10.0)
- Stop the Harbor instance using `docker-compose down` or `kubectl` commands depending on your deployment
- Backup your Harbor data and configuration directory (typically `/harbor` or your persistent volume)
- For Docker Compose deployment: Update the `harbor/values.yaml` or `docker-compose.yml` to use the target version
- For Helm deployment: Run `helm upgrade` with the new chart version or update the image tag to the fixed version
- If on 2.8.x branch: Upgrade to version 2.8.5 or later
- If on 2.9.x branch: Upgrade to version 2.9.3 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-22244 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-22244 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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