Qualys Web App Scanning ConnectorApplication · Jenkins
CVE-2023-39154
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 · uneditedIncorrect permission checks in Jenkins Qualys Web App Scanning Connector Plugin 2.0.10 and earlier allow attackers with global Item/Configure permission to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.
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 Qualys Web App Scanning Connector Plugin versions 2.0.10 and earlier has incorrect permission checks that allow attackers with global Item/Configure permission to connect to attacker-controlled URLs using credential IDs obtained through another method, enabling credential theft from Jenkins.
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
Qualys Web App Scanning ConnectorApplication
<= 2.0.10CVSS 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 Qualys Web App Scanning Connector Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Qualys Web App Scanning Connector' or inspect the plugin directory ($JENKINS_HOME/plugins/) for the qualys-was-connector plugin folderAffected if The plugin is present in the Jenkins instance
-
Determine the installed plugin versionIn Manage Jenkins > Manage Plugins > Installed, find the Qualys Web App Scanning Connector plugin and note the version number listed in the 'Version' columnAffected if The installed version is 2.0.10 or earlier
-
Identify users with global Item/Configure permissionNavigate to Manage Jenkins > Manage Users and cross-reference with Manage Jenkins > Configure Global Security > Authorization to determine which users or groups hold the 'Item/Configure' permission at the global levelAffected if Any user account other than administrators has global Item/Configure permission enabled
-
Check for configured credentials in the pluginNavigate to Manage Jenkins > Manage Credentials and examine any credentials stored under the 'Qualys Web App Scanning' domain or global credentials that could be accessed by users with Item/Configure permissionAffected if Credentials are stored in Jenkins that could be accessed by users with Item/Configure permission
The environment is affected if the Qualys Web App Scanning Connector Plugin version 2.0.10 or earlier is installed AND any non-administrative user has global Item/Configure permission, allowing potential credential theft through attacker-controlled URL connections.
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 Qualys Web App Scanning Connector Plugin version 2.0.11 or later to obtain the fixed permission validation logic.
Fix this in Qualys Web App Scanning Connector
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-39154 — 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-2023-39154 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