CVE-2019-12130
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 · uneditedIn ONAP CLI through Dublin, by accessing an applicable port (30234, 30290, 32010, 30270, 30224, 30281, 30254, 30285, and/or 30271), an attacker gains full access to the respective ONAP services without any authentication. All ONAP Operations Manager (OOM) setups are affected.
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 · high confidenceONAP CLI through the Dublin release contains multiple exposed service ports (30234, 30290, 32010, 30270, 30224, 30281, 30254, 30285, 30271) that provide unauthenticated full access to respective ONAP services. An attacker with network access to these ports can bypass all authentication and gain complete control over affected services.
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>= 3.0.0, <= 4.0.0CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify ONAP installation and versionLocate ONAP deployment files, Helm charts, or container images. Check version metadata in deployment manifests, container labels, or ONAP's internal version endpoint if accessible. Compare against the affected range: >= 3.0.0 and <= 4.0.0.Affected if ONAP version is between 3.0.0 and 4.0.0 (Dublin release)
-
Identify listening ports from the vulnerable listScan the ONAP host or container network for open ports. Specifically check for: 30234, 30290, 32010, 30270, 30224, 30281, 30254, 30285, 30271. Use commands like netstat, ss, or nmap against the ONAP infrastructure.Affected if Any of these nine ports (30234, 30290, 32010, 30270, 30224, 30281, 30254, 30285, 30271) are open and listening
-
Verify network accessibility of vulnerable portsDetermine if these ports are accessible from untrusted network segments. Review Kubernetes NetworkPolicies, firewall rules, or cloud security groups. Attempt a connection test from an untrusted network perspective if authorized.Affected if The ports are accessible from network segments outside the trusted admin boundary
-
Test for unauthenticated access to servicesSend requests to the exposed ports without providing credentials. For each open port, attempt to invoke service APIs or commands without authentication headers or tokens.Affected if Service endpoints respond successfully without requiring authentication credentials
User is affected if ONAP version is between 3.0.0 and 4.0.0 AND any of the nine ports (30234, 30290, 32010, 30270, 30224, 30281, 30254, 30285, 30271) are network-accessible without authentication.
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.
dbcve · scopedImplement authentication controls on all exposed service ports and/or restrict network access via firewall rules/NetworkPolicies. Consider disabling unauthenticated endpoints entirely or upgrading to a patched ONAP version if available.
ONAP El Alto or later release (versions > 4.0.0)
- Upgrade ONAP to a release after the Dublin release (e.g., El Alto or later) to receive the authentication fix
- After upgrade, verify that the affected ports (30234, 30290, 32010, 30270, 30224, 30281, 30254, 30285, 30271) now require authentication
- If immediate upgrade is not possible, implement network-level access controls to restrict access to these ports to authorized IPs only
- Audit existing access to these ports to detect any unauthorized access that may have occurred
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation10.0 h
- Implementation24.0 h
- Testing10.0 h
- Review / QA5.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $13,952.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12130 — 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-12130 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