CVE-2019-16299
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 mobility application (org.onosproject.mobility), the host event listener does not handle the following event types: HOST_ADDED, 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 confidenceIn ONOS 1.14, the mobility application (org.onosproject.mobility) contains a host event listener that fails to handle three event types: HOST_ADDED, HOST_REMOVED, and HOST_UPDATED. This missing event handler code means that when these host-related events occur, the intended logic does not execute, potentially causing unexpected behavior in the network management functions.
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.
-
Confirm ONOS versionRun the ONOS CLI command 'version' or check the ONOS web interface for the installed version number. Alternatively, inspect the ONOS distribution metadata or the Karaf version output.Affected if The installed version is exactly 1.14.0 (ONOS 1.14.0)
-
Verify mobility application is activeIn the ONOS CLI, run 'apps -s' or 'app -a' to list active applications. Look for org.onosproject.mobility in the output.Affected if The mobility application (org.onosproject.mobility) is installed and active in the ONOS instance
-
Inspect host event listener source codeLocate the mobility application source code, specifically the host event listener class within org.onosproject.mobility. Examine the event handler methods for HOST_ADDED, HOST_REMOVED, and HOST_UPDATED event types.Affected if The host event listener class is missing handler implementations for one or more of: HOST_ADDED, HOST_REMOVED, or HOST_UPDATED events
-
Check for host event processing logsReview ONOS log files (in /opt/onos/log/ or equivalent) around the time when hosts are added, removed, or updated on the network. Look for any errors or warnings related to the mobility application handling host events.Affected if Host events occur in the network but the mobility application does not process them (no corresponding logs showing event handling execution)
You are affected if running ONOS 1.14.0 with the mobility application active and the host event listener lacks handler implementations for HOST_ADDED, HOST_REMOVED, or HOST_UPDATED events.
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 dataThe fix requires implementing the missing event handlers for HOST_ADDED, HOST_REMOVED, and HOST_UPDATED events in the mobility application's host event listener to ensure proper code execution when these events fire.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16299 — 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-16299 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