JenkinsApplication · Cloudbees
CVE-2012-6073
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 · uneditedOpen redirect vulnerability in Jenkins before 1.491, Jenkins LTS before 1.480.1, and Jenkins Enterprise 1.424.x before 1.424.6.13, 1.447.x before 1.447.4.1, and 1.466.x before 1.466.10.1 allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via unspecified vectors.
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 confidenceOpen redirect vulnerability in Jenkins allows remote unauthenticated attackers to craft URLs that redirect users to arbitrary external websites. The vulnerability exists in the redirect handling logic, enabling phishing attacks by tricking users into visiting malicious sites via trusted Jenkins URLs.
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
= 1.447.1.1= 1.447.2.2= 1.447.3.1= 1.400= 1.424= 1.447= 1.424.0.2= 1.424.0.4= 1.424.1.1= 1.424.2.1= 1.424.4.1= 1.424.5.1
JenkinsApplication
<= 1.466.2= 1.409.1= 1.409.2= 1.409.3= 1.424.1= 1.424.2= 1.424.3= 1.424.4= 1.424.5= 1.424.6= 1.447.1= 1.447.2CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:M/Au:N/C:P/I:P/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 checksWork through these to decide whether this CVE applies to you.
-
Check Jenkins version from web interfaceVisit the Jenkins main page and look for the version number displayed in the page footer or title areaAffected if The displayed version matches one of the affected versions listed (1.409.x, 1.424.x, 1.447.x, or <=1.466.2 for Jenkins; or specific 1.447.x and 1.424.x versions for Cloudbees)
-
Check Jenkins version via APIAccess the URL /api/json?tree=version or /systemInfo to retrieve version information programmaticallyAffected if The returned version matches any of the affected versions
-
Verify Jenkins build dateCheck the build timestamp in Jenkins under Manage Jenkins > System Information or in the build historyAffected if The build date corresponds to an affected version cycle
-
Test for open redirect behaviorAttempt to access a Jenkins URL with a redirect parameter pointing to an external domain (for example, appending ?from=http://example.com or following known redirect patterns in the application)Affected if The application redirects to an external untrusted domain instead of rejecting or normalizing the redirect target
The environment is affected if the installed Jenkins version matches any of the listed affected versions AND the redirect handling logic is present and processing external redirect targets.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade Jenkins to version 1.491 or later (or LTS 1.480.1+), or apply the appropriate Jenkins Enterprise patches. If upgrading is not immediately feasible, implement URL validation to ensure redirects only allow relative paths or whitelisted domains.
Fix this in Jenkins
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-6073 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-6073 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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