What is CVE-2015-7294?

CVE-2015-7294 is a high-severity security vulnerability in ldapauth-fork (npm), affecting versions < 2.3.3. It is fixed in 2.3.3.

How severe is CVE-2015-7294?

CVE-2015-7294 has a CVSS score of 7.5 (High). 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 packages are affected by CVE-2015-7294?

ldapauth-fork (npm) versions < 2.3.3; ldapauth (npm) versions < 2.2.4.

Is there a fix for CVE-2015-7294?

Yes. CVE-2015-7294 is fixed in 2.3.3. Upgrade to this version or later.

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

Whether CVE-2015-7294 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-7294 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-7294?

Upgrade ldapauth-fork to 2.3.3 or later.

CVE-2015-7294 in ldapauth-fork

Q: How severe is CVE-2015-7294?

CVE-2015-7294 has a CVSS score of 7.5 (High). 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: Which packages are affected by CVE-2015-7294?

ldapauth-fork (npm) versions < 2.3.3; ldapauth (npm) versions < 2.2.4.

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

Yes. CVE-2015-7294 is fixed in 2.3.3. Upgrade to this version or later.

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

Whether CVE-2015-7294 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-7294 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-7294?

Upgrade ldapauth-fork to 2.3.3 or later.

Summary

LDAP Injection in ldapauth

Versions 2.2.4 and earlier of ldapauth-fork are affected by an LDAP injection vulnerability. This allows an attacker to inject and run arbitrary LDAP commands via the username parameter.

Impact

CVE-2015-7294 has a CVSS score of 7.5 (High). 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 (2.3.3); upgrading removes the vulnerable code path.

Affected versions

ldapauth-fork (< 2.3.3) ldapauth (< 2.2.4)

Security releases

ldapauth-fork → 2.3.3 (npm)

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

ldapauth is not actively maintained, having not seen a publish since 2014. As a result, there is no patch available. Consider updating to use ldapauth-fork 2.3.3 or greater.

Frequently Asked Questions

What is CVE-2015-7294? CVE-2015-7294 is a high-severity security vulnerability in ldapauth-fork (npm), affecting versions < 2.3.3. It is fixed in 2.3.3.
How severe is CVE-2015-7294? CVE-2015-7294 has a CVSS score of 7.5 (High). 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 packages are affected by CVE-2015-7294?
- ldapauth-fork (npm) (versions < 2.3.3)
- ldapauth (npm) (versions < 2.2.4)
Is there a fix for CVE-2015-7294? Yes. CVE-2015-7294 is fixed in 2.3.3. Upgrade to this version or later.
Is CVE-2015-7294 exploitable, and should I be worried? Whether CVE-2015-7294 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-7294 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-7294? Upgrade ldapauth-fork to 2.3.3 or later.