CVE-2014-3662

CVE-2014-3662 is a medium-severity security vulnerability in org.jenkins-ci.main:jenkins-core (maven), affecting versions >= 1.566, < 1.583. It is fixed in 1.583, 1.565.3.

Summary

Jenkins before 1.583 and LTS before 1.565.3 allows remote attackers to enumerate user names via vectors related to login attempts.

Impact

Affected versions

org.jenkins-ci.main:jenkins-core (>= 1.566, < 1.583) org.jenkins-ci.main:jenkins-core (< 1.565.3)

Security releases

org.jenkins-ci.main:jenkins-core → 1.583 (maven) org.jenkins-ci.main:jenkins-core → 1.565.3 (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.

See it in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.jenkins-ci.main:jenkins-core to 1.583 or later; org.jenkins-ci.main:jenkins-core to 1.565.3 or later

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

Frequently Asked Questions

  1. What is CVE-2014-3662? CVE-2014-3662 is a medium-severity security vulnerability in org.jenkins-ci.main:jenkins-core (maven), affecting versions >= 1.566, < 1.583. It is fixed in 1.583, 1.565.3.
  2. Which versions of org.jenkins-ci.main:jenkins-core are affected by CVE-2014-3662? org.jenkins-ci.main:jenkins-core (maven) versions >= 1.566, < 1.583 is affected.
  3. Is there a fix for CVE-2014-3662? Yes. CVE-2014-3662 is fixed in 1.583, 1.565.3. Upgrade to this version or later.
  4. Is CVE-2014-3662 exploitable, and should I be worried? Whether CVE-2014-3662 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
  5. What actually determines whether CVE-2014-3662 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.
  6. How do I fix CVE-2014-3662?
    • Upgrade org.jenkins-ci.main:jenkins-core to 1.583 or later
    • Upgrade org.jenkins-ci.main:jenkins-core to 1.565.3 or later

Other vulnerabilities in org.jenkins-ci.main:jenkins-core

Stop the waste.
Protect your environment with Kodem.