CVE-2019-12129
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 MSB 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 MSB (Micro Service Bus) exposes multiple service ports (30234, 30290, 32010, 30270, 30224, 30281, 30254, 30285, 30271) that lack authentication controls, allowing any attacker with network access to gain full administrative control over respective ONAP services without credentials.
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 if ONAP MSB is deployedInventory your environment for ONAP (Open Network Automation Platform) components, specifically looking for the Micro Service Bus (MSB) serviceAffected if ONAP MSB is present in the environment
-
Check ONAP versionLocate the installed ONAP version number and compare it to the affected range: >= 3.0.0 and <= 4.0.0Affected if The installed version falls within 3.0.0 to 4.0.0 inclusive
-
Identify exposed MSB portsScan network listening services or check MSB configuration for any of these ports: 30234, 30290, 32010, 30270, 30224, 30281, 30254, 30285, 30271Affected if Any of these nine ports are listening and accessible from the network
-
Verify authentication configuration on MSB portsExamine the MSB service configuration or documentation to determine whether authentication controls are enabled for the exposed portsAffected if Authentication is not enforced or is disabled on the exposed MSB ports
Environment is affected if ONAP version 3.0.0-4.0.0 is running with MSB service ports exposed and authentication not enabled on those ports.
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 dataEnable and enforce authentication on all MSB service ports, implement network segmentation to restrict access to authorized internal systems only, and apply any available security patches for the Dublin release.
- Consultation12.0 h
- Implementation32.0 h
- Testing20.0 h
- Review / QA10.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $20,736.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12129 — 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-12129 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