Netsparker Cloud ScanApplication · Jenkins
CVE-2019-10290
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 · uneditedA missing permission check in Jenkins Netsparker Cloud Scan Plugin 1.1.5 and older in the NCScanBuilder.DescriptorImpl#doValidateAPI form validation method allowed attackers with Overall/Read permission to initiate a connection to an attacker-specified server.
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 Netsparker Cloud Scan Plugin for Jenkins has a missing permission check in the NCScanBuilder.DescriptorImpl#doValidateAPI form validation method. This allows any user with Overall/Read permission (the lowest privilege level in Jenkins) to trigger the plugin to initiate HTTP connections to attacker-specified servers, leading to potential Server-Side Request Forgery (SSRF) or sensitive data exfiltration.
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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 if Netsparker Cloud Scan plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Netsparker Cloud Scan', or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins | findstr netsparkerAffected if The plugin appears in the installed plugins list
-
Determine the installed version of the Netsparker Cloud Scan pluginIn the Installed plugins tab, locate the Netsparker Cloud Scan plugin and note the Version column; alternatively, check the plugin's manifest file at $JENKINS_HOME/plugins/netsparker-cloud-scan/META-INF/MANIFEST.MFAffected if The version is 1.1.5 or earlier
-
Verify if the doValidateAPI form validation endpoint is reachable without elevated permissionsAttempt an HTTP GET request to the Jenkins URL /descriptorbyname/NCScanBuilder/doValidateAPI using an account that only has Overall/Read permission (or no authentication if anonymous read is enabled); if the endpoint returns a response rather than a 403 Forbidden, the vulnerability is presentAffected if The endpoint responds without requiring permissions beyond Overall/Read
-
Confirm the vulnerability exists by testing SSRF behaviorSubmit a crafted request to /descriptorbyname/NCScanBuilder/doValidateAPI with an attacker-controlled URL parameter (such as ?apiKey=test&scanProfile=test&url=http://attacker-controlled-server) and verify that Jenkins initiates an HTTP connection to that server (observable in logs or network traffic)Affected if Jenkins makes an outbound HTTP request to the attacker-specified URL
The environment is affected if the Netsparker Cloud Scan plugin version is 1.1.5 or earlier and the doValidateAPI endpoint accepts requests from users with only Overall/Read permission.
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 Netsparker Cloud Scan Plugin version 1.1.6 or later which includes the missing permission check. If upgrade is not possible, restrict Overall/Read permission to trusted users only.
Fix this in Netsparker Cloud Scan
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10290 — 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-10290 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