CVE-2019-19029
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 SQL Injection via user-groups 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 confidenceHarbor Container Registry versions prior to 1.8.6 and 1.9.3 contain a SQL injection vulnerability in the user-groups functionality. Attackers can inject malicious SQL statements through user group parameters, potentially allowing unauthorized database access, data exfiltration, or data manipulation.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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.
-
Determine Harbor versionAccess the Harbor API at /api/v2.0/email/ping or check the web UI footer for the version number. If using docker-compose, run 'docker ps' and inspect the harbor-portal or harbor-core container image tags.Affected if Installed version is >= 1.7.0 and < 1.8.6, or >= 1.9.0 and < 1.9.3, or the product is Pivotal VMware Harbor Registry of any version.
-
Verify user-groups API endpoint is accessibleCheck if the Harbor API endpoint /api/v2.0/usergroups is reachable. This endpoint handles user group creation and management.Affected if The user-groups API endpoint is accessible without additional authentication controls beyond standard Harbor auth.
-
Check if LDAP or OIDC user group sync is configuredReview Harbor configuration in harbor.yml or environment variables for 'harbor_admin_password', 'ldap_url', 'ldap_search_dn', and 'oidc_provider_name' settings. These determine if external group sync is enabled.Affected if LDAP or OIDC authentication is enabled with user group synchronization, allowing group parameter injection.
-
Confirm database connectivityExamine Harbor database configuration to determine if the PostgreSQL database used by Harbor is directly accessible from untrusted networks or if the application user has elevated database privileges.Affected if Database is accessible and the application uses a database user with permissions sufficient for SQL injection impact (read/write to sensitive tables).
A user is affected if their Harbor installation version falls within the vulnerable ranges (1.7.0 to <1.8.6, or 1.9.0 to <1.9.3) or is Pivotal VMware Harbor Registry, and the user-groups functionality is accessible for injection.
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 or 1.9.3 or later to remediate the SQL injection vulnerability in the user-groups component.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19029 — 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-19029 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