Resource enumeration via unauthenticated API response discrepancies
Published Dec 26, 2022 · Updated Apr 14, 2025
Information disclosure in CNCF Harbor 1.7.0 through 1.10.2 and 2.0.0 allows remote attackers to enumerate registry resources. Unauthenticated requests to project, repository, chart, label, and metadata API endpoints return status codes that differ according to resource existence. No account or user interaction is required; the bounded impact is disclosure of which projects, repositories, and related registry objects exist.
Summary
What happened
Information disclosure in CNCF Harbor 1.7.0 through 1.10.2 and 2.0.0 allows remote attackers to enumerate registry resources. Unauthenticated requests to project, repository, chart, label, and metadata API endpoints return status codes that differ according to resource existence. No account or user interaction is required; the bounded impact is disclosure of which projects, repositories, and related registry objects exist.
The record
- CVE
- CVE-2019-19030
- Published
- Dec 26, 2022
- Updated
- Apr 14, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-204
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 26, 2022CVE publishedPublication date reported by the CVE source.
- Apr 14, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo