What is CVE-2015-1778?

CVE-2015-1778 is a critical-severity improper authentication vulnerability in org.opendaylight.odlparent:opendaylight-karaf-resources (maven), affecting versions < 0.2.3-Helium-SR3. It is fixed in 0.2.3-Helium-SR3. The application does not adequately verify the identity of a user, device, or process before granting access.

How severe is CVE-2015-1778?

CVE-2015-1778 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Is there a fix for CVE-2015-1778?

Yes. CVE-2015-1778 is fixed in 0.2.3-Helium-SR3. Upgrade to this version or later.

Is CVE-2015-1778 exploitable, and should I be worried?

Whether CVE-2015-1778 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2015-1778 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2015-1778

Q: How severe is CVE-2015-1778?

CVE-2015-1778 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Is there a fix for CVE-2015-1778?

Yes. CVE-2015-1778 is fixed in 0.2.3-Helium-SR3. Upgrade to this version or later.

Q: Is CVE-2015-1778 exploitable, and should I be worried?

Whether CVE-2015-1778 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2015-1778 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2015-1778?

Upgrade org.opendaylight.odlparent:opendaylight-karaf-resources to 0.2.3-Helium-SR3 or later.

Summary

Opendaylight will authenticate any username and password combination

The custom authentication realm used by karaf-tomcat's "opendaylight" realm in Opendaylight before Helium SR3 will authenticate any username and password combination.

Impact

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

CVE-2015-1778 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.2.3-Helium-SR3); upgrading removes the vulnerable code path.

Affected versions

org.opendaylight.odlparent:opendaylight-karaf-resources (< 0.2.3-Helium-SR3)

Security releases

org.opendaylight.odlparent:opendaylight-karaf-resources → 0.2.3-Helium-SR3 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade org.opendaylight.odlparent:opendaylight-karaf-resources to 0.2.3-Helium-SR3 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2015-1778? CVE-2015-1778 is a critical-severity improper authentication vulnerability in org.opendaylight.odlparent:opendaylight-karaf-resources (maven), affecting versions < 0.2.3-Helium-SR3. It is fixed in 0.2.3-Helium-SR3. The application does not adequately verify the identity of a user, device, or process before granting access.
How severe is CVE-2015-1778? CVE-2015-1778 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of org.opendaylight.odlparent:opendaylight-karaf-resources are affected by CVE-2015-1778? org.opendaylight.odlparent:opendaylight-karaf-resources (maven) versions < 0.2.3-Helium-SR3 is affected.
Is there a fix for CVE-2015-1778? Yes. CVE-2015-1778 is fixed in 0.2.3-Helium-SR3. Upgrade to this version or later.
Is CVE-2015-1778 exploitable, and should I be worried? Whether CVE-2015-1778 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2015-1778 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2015-1778? Upgrade org.opendaylight.odlparent:opendaylight-karaf-resources to 0.2.3-Helium-SR3 or later.