Sqlplus Script RunnerApplication · Jenkins
CVE-2020-2312
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 · uneditedJenkins SQLPlus Script Runner Plugin 2.0.12 and earlier does not mask a password provided as command line argument in build logs.
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 confidenceThe Jenkins SQLPlus Script Runner Plugin versions 2.0.12 and earlier passes database passwords as command-line arguments to the SQLPlus executable. These passwords are recorded in plaintext within Jenkins build logs, allowing any user with build log access to view the exposed credentials.
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
Sqlplus Script RunnerApplication
<= 2.0.12CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Verify SQLPlus Script Runner Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'SQLPlus Script Runner' or 'Sqlplus Script Runner'Affected if The plugin appears in the installed list and the version is 2.0.12 or lower
-
Identify the exact plugin versionClick on the SQLPlus Script Runner plugin in the installed plugins list and note the Version field displayedAffected if The version shown is 2.0.12 or any version lower (for example 2.0.11, 2.0.10, etc.)
-
Review recent build logs for exposed credentialsOpen a recent build that uses the SQLPlus Script Runner, navigate to the Console Output, and search for plaintext passwords that may have been passed as arguments to sqlplusAffected if Plaintext passwords appear in the build console output, typically near sqlplus command invocations
-
Check historical build logs proactivelyUse Jenkins search or log parser to scan past build logs for patterns like 'sqlplus' combined with credential-like strings (passwords, connection strings with passwords)Affected if Any historical build logs contain plaintext passwords used with SQLPlus operations
You are affected if the SQLPlus Script Runner Plugin version 2.0.12 or lower is installed AND any build logs contain plaintext database passwords passed to SQLPlus.
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 to a patched version of the SQLPlus Script Runner Plugin once available, or rotate any credentials that may have been exposed through build logs. Consider using Jenkins credentials binding or environment variables instead of command-line arguments for sensitive values.
Fix this in Sqlplus Script Runner
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2312 — 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-2020-2312 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