CVE-2019-10289 json
CSRF vulnerability in Jenkins Netsparker Enterprise Scan Plugin
published 7y ago modified 4mo ago also GHSA-qc3m-6xmq-7hrj , EUVD-2022-4942
- cvss
- 6.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 71%
- public exploits
- 0
- none known
Summary
A cross-site request forgery vulnerability in Jenkins Netsparker Cloud Scan Plugin 1.1.5 and older in the NCScanBuilder.DescriptorImpl#doValidateAPI form validation method allowed attackers to initiate a connection to an attacker-specified server.
Patch / fix
- maven org.jenkins-ci.plugins:netsparker-cloud-scan 1.1.6
Is CVE-2019-10289 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.34% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
| GitHub | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jenkins-ci.plugins:netsparker-cloud-scan | <1.1.6 |
1.1.6 |
Affected products
- Jenkins project Jenkins Netsparker Cloud Scan Plugin
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
jenkins.io
/security/advisory/2019-04-03/#SECURITY-1032
web, vendor-advisory
-
securityfocus.com
/bid/107790
vdb-entry, web, third-party-advisory
-
openwall.com
/lists/oss-security/2019/04/12/2
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-10289
advisory
Sources
- CVE List CVE-2019-10289
- GitHub Advisory GHSA-qc3m-6xmq-7hrj
- NVD CVE-2019-10289
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.