How severe is CVE-2017-1000406?

CVE-2017-1000406 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2017-1000406?

CVE-2017-1000406 affects the following packages: org.opendaylight.integration:distribution-karaf (Maven). Ecosystems affected: Maven.

How do I fix CVE-2017-1000406?

The records we use list no patched version of org.opendaylight.integration:distribution-karaf for CVE-2017-1000406. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2017-1000406 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.opendaylight.integration:distribution-karaf, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2017-1000406 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2017-1000406 actively exploited in the wild?

No public exploit code has been indexed for CVE-2017-1000406 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2017-1000406?

CVE-2017-1000406 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 65th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2017-1000406?

CVE-2017-1000406 is classified as CWE-254 (CWE-254). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2017-1000406 published, and has it been updated?

CVE-2017-1000406 was published on May 17, 2022 and was last updated on December 8, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2017-1000406 — distribution-karaf

HIGH

CVE-2017-1000406 is a high-severity (CVSS 7.5) CWE-254 vulnerability in org.opendaylight.integration:distribution-karaf. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Password change doesn't result in Karaf clearing cache

Published

May 17, 2022

Updated

Dec 8, 2024

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs65th percentile — riskier than 65% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕org.opendaylight.integration:distribution-karaf

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

OpenDaylight 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).

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.opendaylight.integration:distribution-karaf`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

karafopendaylight

1 version

0.6.1-carbon

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.opendaylight.integration:distribution-karaf, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of org.opendaylight.integration:distribution-karaf for CVE-2017-1000406. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

OpenDaylight 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).

O3 Security · Impact-Aware SCA

Is CVE-2017-1000406 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works