CVE-2019-16298
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 · uneditedAn issue was discovered in Open Network Operating System (ONOS) 1.14. In the virtual broadband network gateway application (org.onosproject.virtualbng), the host event listener does not handle the following event types: HOST_MOVED, HOST_REMOVED, HOST_UPDATED. In combination with other applications, this could lead to the absence of intended code execution.
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 · moderate confidenceThe virtual broadband network gateway application (org.onosproject.virtualbng) in ONOS 1.14 contains a host event listener that fails to handle three specific event types: HOST_MOVED, HOST_REMOVED, and HOST_UPDATED. This omission means the application does not execute intended logic when these host-related events occur, potentially causing inconsistent network state management when combined with other ONOS applications.
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= 1.14.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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Verify ONOS version is 1.14.0Run 'onos-version' command or check the ONOS admin UI version displayAffected if The installed ONOS version equals 1.14.0 exactly
-
Confirm virtualbng application is installedRun 'onos-apps' command or check the applications list in the ONOS CLI using 'apps -s' to list installed applicationsAffected if org.onosproject.virtualbng appears in the installed applications list
-
Identify virtualbng host event listener sourceLocate the Java source file containing the HostListener implementation within the virtualbng application bundle (typically in src/main/java/org/onosproject/virtualbng/...)Affected if The application bundle contains a HostListener class
-
Inspect event handler methodsExamine the HostListener implementation for @Override methods handling HostEvent events - specifically look for methods handling HOST_MOVED, HOST_REMOVED, and HOST_UPDATED event typesAffected if The HostListener implements onEvent or similar methods that do NOT include handlers for HOST_MOVED, HOST_REMOVED, and HOST_UPDATED event types (only other event types like HOST_ADDED are handled)
User is affected if running ONOS 1.14.0 with the virtualbng application installed and the HostListener class lacks event handlers for HOST_MOVED, HOST_REMOVED, and HOST_UPDATED event types.
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 dataImplement event handlers for HOST_MOVED, HOST_REMOVED, and HOST_UPDATED event types in the virtualbng application's host event listener to ensure proper code execution when these events are triggered.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16298 — 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-16298 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