CVE-2019-19025
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 · uneditedCloud Native Computing Foundation Harbor prior to 1.8.6 and 1.9.3 allows CSRF in the VMware Harbor Container Registry for the Pivotal Platform.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in Harbor Container Registry allows attackers to induce authenticated users to perform unintended actions on the registry, potentially modifying configurations, user permissions, or project settings.
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>= 1.7.0, < 1.8.6>= 1.9.0, < 1.9.3all versionsCVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 Harbor versionAccess the Harbor API endpoint /api/v2.0/ping or check the web interface footer for the version number. If running as a container, run 'docker ps' to find the harbor-portal or harbor-core container, then inspect with 'docker inspect <container>' to find the image version tag.Affected if The version displayed is 1.7.0 through 1.8.5 (inclusive), or 1.9.0 through 1.9.2 (inclusive), or unknown/undetermined from a Pivotal VMware Harbor installation
-
Confirm Harbor distributionCheck the product name displayed in the Harbor web UI login page or check the container image names with 'docker images' or 'podman images' to identify if the installation is the Pivotal VMware Harbor distribution.Affected if The installation is identified as Pivotal VMware Harbor Registry (all versions are affected regardless of version number)
-
Check session configurationInspect Harbor's configuration files or environment variables for CSRF token settings. In Harbor deployments, verify that the application is configured to validate CSRF tokens on state-changing API requests.Affected if CSRF protection is not enforced or the configuration allows stateless requests to modify user permissions, project settings, or system configurations
You are affected if your Harbor installation version is 1.7.0-1.8.5, 1.9.0-1.9.2, or any version of Pivotal VMware Harbor Registry, as these lack proper CSRF protection for authenticated user sessions.
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.
From vendor data1.8.61.9.3
Upgrade Harbor to version 1.8.6, 1.9.3, or later which contain the CSRF protection fixes.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19025 — 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-2019-19025 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