Password change doesn't result in Karaf clearing cache

published 2017-11-30 8 y ago modified 2026-06-17 4 mo ago also GHSA-4px2-gqhv-mrc7 , EUVD-2022-2423

cvss: 7.5; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.1%; EPSS 1.1% chance of exploitation in 30 days, percentile 65%
public exploits: 0; none known

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

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-1000406 updated 2026-05-13 cvss 7.5

opendaylight: Previous password continues to work after password change

Red Hat OpenStack Platform 11 (Ocata) opendaylight Red Hat OpenStack Platform 12 (Pike) opendaylight
affected: no fix planned “Will not fix”
Red Hat OpenStack Platform 13 (Queens) opendaylight
affected: no fix available
Red Hat OpenStack Platform 8 (Liberty) opendaylight Red Hat OpenStack Platform 9 (Mitaka) opendaylight Red Hat OpenStack Platform 10 (Newton) opendaylight
not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.09% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
NVD	3.0	7.5	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:N/I:P/A:N
GitHub	3.0	7.5	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem	package	affected	fixed in
maven	org.opendaylight.integration:distribution-karaf	<=0.6.4-Carbon	no fix listed

Classification

Weakness

CWE-254 7PK - Security Features

References

git.opendaylight.org /gerrit/#/q/topic:AAA-151
web, vendor-advisory
jira.opendaylight.org /browse/AAA-151
web, issue-tracking, vendor-advisory
seclists.org /oss-sec/2017/q4/320
mailing-list, web, third-party-advisory
nvd.nist.gov /vuln/detail/CVE-2017-1000406
advisory
git.opendaylight.org /gerrit
package

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary