CVE-2024-46943
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 OpenDaylight Authentication, Authorization and Accounting (AAA) through 0.19.3. A rogue controller can join a cluster to impersonate an offline peer, even if this rogue controller does not possess the complete cluster configuration information.
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 confidenceA vulnerability in OpenDaylight AAA (versions through 0.19.3) allows a rogue controller to join a cluster and impersonate an offline peer without possessing complete cluster configuration. This cluster authentication weakness enables unauthorized nodes to gain cluster membership and assume the identity of legitimate offline controllers, bypassing proper credential validation.
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<= 0.19.3CVSS 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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 AAA versionCheck the OpenDaylight AAA bundle version by examining the karaf features.xml or the MANIFEST.MF file in the AAA feature JAR, typically found in the OpenDaylight distribution under distribution/karaf/target/assembly/system/org/opendaylight/aaa/Affected if The AAA version is 0.19.3 or earlier (any version through 0.19.3)
-
Verify cluster features are enabledLog into the OpenDaylight Karaf console and run 'feature:list | grep -i cluster' to list installed cluster-related features, or check the etc/featuresBoot.d configuration file for cluster feature namesAffected if Cluster features (such as odl-clustering or related AAA clustering modules) are installed and active
-
Review cluster topology configurationExamine the distributed datastore configuration files in the etc/opendaylight/karaf/ directory or check the cluster topology using the 'cluster: Topology' command in the Karaf console if availableAffected if The cluster has fewer than the expected number of configured members, or there are unexpected nodes present in the cluster topology
-
Check cluster membership logsSearch controller logs (logs/karaf.log or similar) for cluster join events, looking for messages containing 'cluster' and 'member-joined' or 'controller-joined' entries, especially around times when legitimate controllers were offlineAffected if There are cluster join events from controllers that cannot be verified as legitimate or that occurred when expected peers were offline
-
Inspect cluster authentication configurationReview configuration files in etc/ directory related to cluster security, such as akka.conf, module-shards.conf, or any cluster-specific security configuration filesAffected if Cluster authentication uses weak or no credential validation, or if the configuration appears incomplete or missing cluster shared secrets
A defender is affected if they run OpenDaylight AAA version 0.19.3 or earlier with cluster features enabled, and their cluster topology or logs show unexpected membership or unauthenticated join 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 dataApply the available patch for AAA 0.19.3 or later. Review cluster join authentication configurations and implement stricter credential validation for cluster membership to prevent unauthorized controller impersonation.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46943 — 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-46943 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