dbcve.org
JenkinsApplication

CVE-2012-4439

MEDIUM · 6.1 CVSS v3.1 Published 2019-11-18
Fix available
A fix is available. Upgrade to 1.466.2 / 1.482 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cross-site Scripting (XSS) in Jenkins main before 1.482 and LTS before 1.466.2 allows remote attackers to inject arbitrary web script or HTML via a crafted URL that points to Jenkins.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Cross-site scripting (XSS) vulnerability in Jenkins web interface allowing remote attackers to inject arbitrary web script or HTML via a crafted URL. Affects Jenkins main line before version 1.482 and LTS before version 1.466.2.

MitigationUpgrade Jenkins to version 1.482 or later (main line) or 1.466.2 or later (LTS) to apply the security fix for this XSS vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JenkinsApplication
Affected:< 1.466.2< 1.482

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Jenkins is deployed
    Check if Jenkins is running by accessing the web interface at the typical port (8080) or checking for Jenkins processes: ps aux | grep jenkins or systemctl status jenkins
    Affected if Jenkins is not present in the environment, this CVE does not apply
  2. Locate Jenkins installation directory
    Common paths: /var/lib/jenkins (Linux), C:\Program Files\Jenkins (Windows), or check the process command line for the jenkins.war location
    Affected if Cannot locate Jenkins installation to inspect version
  3. Check installed Jenkins version via CLI
    Run: java -jar /path/to/jenkins.war --version (replace /path/to/jenkins.war with actual path) or check /var/lib/jenkins/jenkins.war --version
    Affected if Command fails or version cannot be determined
  4. Check version from web interface
    Log into Jenkins dashboard and look at the footer text which displays the version number (e.g., 'Jenkins 1.481')
    Affected if Cannot access web interface but Jenkins is running
  5. Compare version against CVE affected ranges
    If version is 1.466.x or lower, or 1.467 through 1.481, the instance is affected. LTS versions below 1.466.2 and main line versions below 1.482 are vulnerable
    Affected if Installed version is Jenkins < 1.466.2 (LTS) or Jenkins < 1.482 (main line)

The environment is affected if the installed Jenkins version is lower than 1.466.2 for LTS releases or lower than 1.482 for main line releases.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 1.466.2 / 1.482 or later
Fixed in 1.466.21.482
Interim mitigation

Upgrade Jenkins to version 1.482 or later (main line) or 1.466.2 or later (LTS) to apply the security fix for this XSS vulnerability.

Fix this in Jenkins Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-4439 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-4439 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data