CVE-2018-1999032 — pangolin-testrail-connect…
MEDIUMFix: jenkinsci/pangolin-testrail-connector-plugin@53dac44CVE-2018-1999032 is a medium-severity (CVSS 6.5) Improper Privilege Management vulnerability in org.jenkins-ci.plugins:pangolin-testrail-connector. A fix is available for org.jenkins-ci.plugins:pangolin-testrail-connector — see the affected versions and patch details below.
Jenkins Agiletestware Pangolin Connector for TestRail Plugin CSRF vulnerability and missing permission checks
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.jenkins-ci.plugins:pangolin-testrail-connectorReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
A data modification vulnerability exists in Jenkins Agiletestware Pangolin Connector for TestRail Plugin 2.1 and earlier in GlobalConfig.java that allows attackers with Overall/Read permission to override this plugin's configuration by sending crafted HTTP requests to an unprotected endpoint.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.plugins:pangolin-testrail-connector | all versions | 2.2org.jenkins-ci.plugins:pangolin-testrail-connector:2.2 |
Affected Products
pangolin connector for testrailagiletestwareDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:pangolin-testrail-connector, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:pangolin-testrail-connector to 2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-1999032 is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.
Frequently Asked Questions
Is CVE-2018-1999032 in your dependencies?
Find it across Maven, including transitive dependencies.