Netsparker Cloud ScanApplication · Jenkins
CVE-2019-10291
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 Netsparker Cloud Scan Plugin 1.1.5 and older stored credentials unencrypted in its global configuration file on the Jenkins master where they could be viewed by users with access to the master file system.
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 Netsparker Cloud Scan Plugin versions 1.1.5 and older stores credentials in plaintext within its global configuration file on the Jenkins master file system. Any user with access to the master file system can read these unencrypted credentials, leading to credential disclosure.
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
Netsparker Cloud ScanApplication
<= 1.1.5CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 Netsparker Cloud Scan Plugin versionNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Netsparker Cloud Scan' to view the installed version, or inspect the plugin manifest file at $JENKINS_HOME/plugins/netsparker-cloud-scan/META-INF/MANIFEST.MFAffected if The installed version is 1.1.5 or older
-
Locate the plugin global configuration fileNavigate to the Jenkins home directory and find the configuration file at $JENKINS_HOME/org.jenkinsci.plugins.netsparkercloudscan.NetsparkerCloudScanPlugin.xml, or check the plugin directory for configuration files containing 'netsparkercloudscan' in the filenameAffected if The configuration file exists on the Jenkins master file system
-
Inspect configuration file for plaintext credentialsOpen the configuration file found in the previous step using a text editor or file viewer and search for credential fields (such as apiKey, password, secretKey, or similar sensitive field names) and check if their values appear as plaintext strings rather than encrypted or masked valuesAffected if Credential values in the configuration file are stored as readable plaintext strings rather than being encrypted or obfuscated
A user is affected if the Netsparker Cloud Scan Plugin version is 1.1.5 or older AND the plugin configuration file exists with plaintext credentials stored in it.
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 dataUpdate the Netsparker Cloud Scan Plugin to a version that encrypts stored credentials. Rotate all credentials that may have been exposed, as they were stored in plaintext accessible via file system access.
Fix this in Netsparker Cloud Scan
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10291 — 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-2019-10291 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