CVE-2024-46942
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 OpenDaylight Model-Driven Service Abstraction Layer (MD-SAL) through 13.0.1, a controller with a follower role can configure flow entries in an OpenDaylight clustering deployment.
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 OpenDaylight MD-SAL clustering deployments, a controller with follower role incorrectly possesses write permissions to configure flow entries, which should be restricted to the leader role only. This allows an unauthorized follower to modify network flow configurations, bypassing the intended role-based access control in clustered deployments.
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<= 13.0.1CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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.
-
Identify installed OpenDaylight versionCheck the OpenDaylight release version using the distribution's version file or Karaf console 'list' command. Compare against affected range <= 13.0.1Affected if The installed version is 13.0.1 or lower
-
Confirm MD-SAL clustering is enabledInspect the MD-SAL clustering configuration files (typically in etc/ folder of the OpenDaylight distribution) to verify clustering is activeAffected if MD-SAL clustering is enabled and configured
-
Identify controller roles in the clusterExamine the cluster topology or role assignment configuration to determine which node is designated as leader and which are followersAffected if Multiple controllers exist with leader-follower role assignment
-
Verify follower role permissions on flow configurationReview the access control or role permission settings for the MD-SAL data store to check if follower roles have write/create/update permissions to flow-related dataAffected if Follower role nodes have write permissions enabled for flow entry configuration
A user is affected if they run OpenDaylight <= 13.0.1 with MD-SAL clustering enabled and the follower role nodes have write permissions to flow entries.
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 · scopedRestrict follower role to read-only operations in MD-SAL clustering configuration; ensure only the designated leader can configure flow entries. Verify role permissions align with the leader-follower architecture design.
14.0.0 or later stable release
- Verify current MD-SAL version by checking the opendaylight-karaf version or inspecting the yang tools and md-sal artifacts in your deployment
- Review OpenDaylight release notes and security advisories at docs.opendaylight.org or lf-opendaylight.atlassian.net for version 13.0.2 or later
- Upgrade to the latest stable MD-SAL version (14.0.0 or later) that includes the authorization fix
- After upgrade, verify that follower-role controllers in clustering deployments can no longer modify flow entries
- Test clustering failover behavior to ensure proper role-based authorization is enforced
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46942 — 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-2024-46942 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