CVE-2015-1610
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 · uneditedhosttracker in OpenDaylight l2switch allows remote attackers to change the host location information by spoofing the MAC address, aka "topology spoofing."
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 hosttracker component in OpenDaylight l2switch lacks proper validation of host location updates, allowing remote attackers to spoof MAC addresses and falsify the network topology by claiming a host exists at a different location. This topology spoofing can mislead other network control plane functions that rely on accurate host location data.
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 dataall versionsCVSS 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
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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 OpenDaylight installationVerify OpenDaylight controller is installed and running in the environment. Check for ODL processes or service status.Affected if OpenDaylight controller is present and running
-
Identify L2switch feature presenceCheck if the L2switch feature/module is installed in OpenDaylight. This can be verified via Karaf shell using 'feature:list | grep l2switch' or by reviewing installed features configuration.Affected if L2switch feature is installed in OpenDaylight
-
Verify hosttracker component statusCheck if the hosttracker component is active within the L2switch module. In Karaf shell, use 'bundle:list | grep hosttracker' to confirm the component is loaded and running.Affected if hosttracker component is loaded and active in the controller
-
Inspect host location update configurationReview hosttracker configuration files and settings for any validation or authentication mechanisms for host location updates. Look for hosttracker-related XML configs in the ODL configuration directory.Affected if No host location validation or authentication mechanism is configured for hosttracker
-
Check for topology spoofing indicatorsReview network topology data reported by the controller for unexpected or unauthorized host location entries. Compare actual network topology against what ODL reports.Affected if Topology data shows hosts at locations inconsistent with actual network infrastructure
If OpenDaylight with L2switch hosttracker is running without host location validation configured, the environment is vulnerable to MAC spoofing and topology falsification attacks.
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 authentication and validation for host location updates in the hosttracker, or add mechanisms to verify that host location claims originate from legitimate network attachment points.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1610 — 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-2015-1610 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