CVE-2017-1000406
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 · uneditedOpenDaylight Karaf 0.6.1-Carbon fails to clear the cache after a password change, allowing the old password to be used until the Karaf cache is manually cleared (e.g. via restart).
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 confidenceOpenDaylight Karaf 0.6.1-Carbon caches user credentials in memory and fails to invalidate cached authentication tokens when a password is changed. This allows the old password to remain valid for authentication until the Karaf cache is manually cleared (e.g., via restart), creating an authentication bypass window.
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.6.1-carbonCVSS 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.0/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 Karaf versionRun 'karaf --version' or check the Karaf manifest/version file in the installation directory. Common locations: /opt/karaf/etc/org.apache.karaf.version or check the version displayed on Karaf console startup.Affected if Installed version is exactly 0.6.1-carbon (note: only this specific version is affected, not other Carbon versions or other releases)
-
Verify password change activityReview Karaf audit logs or authentication system logs for recent password modification events. Check /opt/karaf/data/log/*.log or the Karaf console audit trail if enabled.Affected if A password change was performed on any user account since the last Karaf restart
-
Check authentication cache stateInspect the Karaf JAAS authentication configuration in /opt/karaf/etc/org.ops4j.pax.web.cfg or similar JAAS configuration files. Look for cached authentication realms.Affected if JAAS realm with credential caching is configured and a password was changed without restarting Karaf
-
Test old credential validityAttempt authentication using the old password for a user account that had its password changed. This requires knowing the previous password.Affected if Old password still successfully authenticates after a password change without Karaf restart
You are affected if running OpenDaylight Karaf exactly version 0.6.1-carbon and any user password was changed without restarting the Karaf instance, allowing the old password to remain valid.
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 dataAfter any password change in OpenDaylight Karaf, restart the Karaf instance or manually clear the cache to invalidate old credentials. Consider implementing automated credential invalidation on password change or upgrading if a patched version is available.
- 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-2017-1000406 — 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-2017-1000406 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