Security readout for executives and security teams
Plain-English summary
This is an information disclosure issue in Harbor. Unauthenticated API behavior can reveal whether a resource exists through different HTTP status codes. It does not indicate data modification or system takeover, but it can help an attacker map registry resources before another attack.
Executive priority
Treat this as a moderate-priority cleanup item, higher if Harbor is internet-facing or stores sensitive container images. It mainly supports reconnaissance, but registry discovery can materially assist later attacks against software supply chains.
Technical view
CVE-2019-19030 is CWE-204 observable response discrepancy in CNCF Harbor before 1.10.3 and 2.x before 2.0.1. The CVSS 3.1 score is 5.3: network-exploitable, low complexity, no privileges or user interaction, with low confidentiality impact only.
Likely exposure
Exposure is likely for organizations running Harbor versions before 1.10.3 or 2.x before 2.0.1, especially where Harbor API endpoints are reachable by unauthenticated or untrusted network users. The provided affected CPE data is incomplete.
Exploitation context
The source bundle does not identify active exploitation, and KEV is false. The risk is reconnaissance: attackers may infer whether Harbor resources exist without authentication, which can improve targeting but is not itself described as direct compromise.
Researcher notes
Evidence supports resource enumeration via unauthenticated API status-code differences. Public sources provided do not include exploit details, observed exploitation, or affected CPEs. Validation should focus on version confirmation, exposure review, and vendor advisory alignment.
Mitigation direction
- Upgrade Harbor to 1.10.3, 2.0.1, or a later supported release.
- Review the Harbor security advisory for vendor-specific remediation guidance.
- Reduce unauthenticated network exposure to Harbor APIs where operationally feasible.
- Prioritize internet-facing or partner-accessible Harbor instances first.
Validation and detection
- Inventory all Harbor instances and record exact version numbers.
- Confirm no instance runs below 1.10.3 or 2.0.1 for 2.x deployments.
- Review external exposure of Harbor API endpoints.
- Use approved vulnerability scanning or vendor checks to confirm remediation.
- Document any unsupported or deferred upgrades as accepted risk.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-204: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2019-19030 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/goharbor/harbor/security/advisories/GHSA-q9x4-q76f-5h5jCVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Observable Response Discrepancy
Observable Response Discrepancy represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.