Loading vulnerability…
Cloud Native Computing Foundation Harbor before 1.10.3 and 2.x before 2.0.1 contains an information disclosure vulnerability in which unauthenticated API requests reveal whether specific resources exist based on differing HTTP status codes. By probing Harbor API endpoints for projects, repositories, and related objects, an attacker can distinguish valid from invalid resources without authentication, enabling enumeration of the Harbor environment.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a proof-of-concept exploit for CVE-2019-19030, targeting VMware Harbor container registry versions less than 1.10.3 and 2.0.1. The exploit is implemented as a Bash script ('boatcrash.sh') that, when provided with a Harbor domain name, uses the Harbor API to enumerate all projects (repositories) and their tags. It then pulls all available Docker images from the target Harbor instance to the attacker's local machine. The script leverages 'curl' for HTTP requests, 'jq' for JSON parsing, and 'docker' to pull images. The README provides usage instructions and a disclaimer. The exploit demonstrates the ability to enumerate and extract Docker images from vulnerable Harbor instances, potentially exposing sensitive environment variables and secrets contained within those images. The main attack vector is network-based, targeting the Harbor API endpoints over HTTPS. No hardcoded credentials or IPs are present; the script requires the user to supply the target domain.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.