dbcve.org
Policy ComplianceApplication · Qualys

CVE-2023-6148

MEDIUM · 5.4 CVSS v3.1 Published 2024-01-09
Fix available
A fix is available. Upgrade to after 1.0.5 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Qualys Jenkins Plugin for Policy Compliance prior to version and including 1.0.5 was identified to be affected by a security flaw, which was missing a permission check while performing a connectivity check to Qualys Cloud Services. This allowed any user with login access and access to configure or edit jobs to utilize the plugin to configure a potential rouge endpoint via which it was possible to control response for certain request which could be injected with XSS payloads leading to XSS while processing the response data

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 confidence

The Qualys Jenkins Plugin for Policy Compliance versions up to and including 1.0.5 lacks proper permission checks during connectivity verification to Qualys Cloud Services. Authenticated users with job configuration privileges can configure a malicious endpoint that returns XSS payloads, which are then executed when the plugin processes the response data.

MitigationUpgrade the Qualys Jenkins Plugin to a version beyond 1.0.5. Additionally, restrict job configuration permissions to only trusted users until the patch is applied.

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
Policy ComplianceApplication
Affected:<= 1.0.5

CVSS 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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Qualys Jenkins Plugin is installed
    Navigate to Jenkins UI > Manage Jenkins > Manage Plugins > Installed tab and search for 'qualys' or 'policy compliance'. Alternatively, list files in $JENKINS_HOME/plugins/ directory for a plugin folder starting with 'qualys'.
    Affected if The Qualys Jenkins Plugin for Policy Compliance is present in the plugin list.
  2. Determine installed plugin version
    In Jenkins UI, click on the plugin from the Installed tab to view its version. From the file system, examine the MANIFEST.MF file inside the plugin's .jpi or .hpi file located in $JENKINS_HOME/plugins/.
    Affected if The plugin version is 1.0.5 or lower.
  3. Identify jobs using the plugin
    Review Jenkins jobs that utilize the Qualys Policy Compliance plugin. Navigate to each job's configuration page and look for Qualys-related build steps or post-build actions related to Policy Compliance or cloud connectivity.
    Affected if Jobs exist that have Qualys Policy Compliance plugin configuration enabled.
  4. Check connectivity verification configuration
    In the job configuration page, locate the Qualys connectivity verification settings. These are typically found under Build Steps or Post-build Actions where Qualys Cloud Platform connection parameters are defined.
    Affected if The plugin has connectivity verification configured and enabled for a Qualys endpoint.

The environment is affected if the Qualys Jenkins Plugin version 1.0.5 or lower is installed AND jobs exist with the plugin's connectivity verification feature configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.0.5
Interim mitigation

Upgrade the Qualys Jenkins Plugin to a version beyond 1.0.5. Additionally, restrict job configuration permissions to only trusted users until the patch is applied.

Recommended fix Moderate confidence

Version greater than 1.0.5 (latest available Qualys Policy Compliance plugin version)

  1. 1. Identify all Jenkins instances using the Qualys Policy Compliance plugin
  2. 2. Verify current plugin version is <= 1.0.5 via Jenkins Plugin Manager
  3. 3. Backup Jenkins configuration before any changes
  4. 4. Upgrade Qualys Policy Compliance plugin to the latest available version via Jenkins Plugin Manager or Jenkins CLI
  5. 5. After upgrade, verify the missing permission check has been addressed by reviewing plugin release notes
  6. 6. Confirm XSS vulnerability is remediated by testing that injected payloads in the connectivity check endpoint are properly sanitized/escaped
Caveat Review plugin release notes for any configuration or feature changes that may require updates to existing job configurations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Policy Compliance Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-6148 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-6148 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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