dbcve.org
Policy ComplianceApplication · Qualys

CVE-2023-6147

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

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 to configure or edit jobs to utilize the plugin and configure potential a rouge endpoint via which it was possible to control response for certain request which could be injected with XXE payloads leading to XXE 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 · moderate confidence

The Qualys Jenkins Plugin for Policy Compliance versions up to and including 1.0.5 lacks proper authorization checks when performing connectivity checks to Qualys Cloud Services. This allows any authenticated user with job configuration or edit permissions to specify a rogue endpoint. The plugin then processes responses from this controlled endpoint without proper validation, enabling XXE (XML External Entity) injection payloads to be processed, leading to XXE vulnerabilities.

MitigationUpgrade the Qualys Jenkins Plugin for Policy Compliance to version 1.0.6 or later, which includes proper permission checks and sanitization of endpoint responses to prevent XXE attacks. Review existing job configurations for any unauthorized endpoint settings.

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
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 checks

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

  1. Verify Qualys Policy Compliance plugin is installed
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed and search for 'Qualys Policy Compliance' or check the $JENKINS_HOME/plugins directory for the qualys-plugin folder
    Affected if The plugin is present in the Jenkins instance
  2. Identify the installed plugin version
    In Jenkins plugin manager, click on the Qualys Policy Compliance plugin to view its version, or read the META-INF/MANIFEST.MF file inside the plugin .hpi file
    Affected if Version is 1.0.5 or lower (any version up to and including 1.0.5)
  3. Review configured jobs for Qualys plugin usage
    Navigate to Jenkins jobs and inspect each job's configuration for Qualys Policy Compliance build steps or post-build actions, particularly looking for fields related to Qualys endpoint or API configuration
    Affected if Any job contains Qualys Policy Compliance build steps with configurable endpoint settings
  4. Check for unauthorized or external endpoint configurations
    In job configuration pages that use the Qualys plugin, examine any endpoint URL fields, host fields, or API connection settings for values pointing to unexpected or external systems rather than official Qualys Cloud Services
    Affected if A job configuration specifies a custom or rogue endpoint URL controlled by an attacker

A user is affected if the Qualys Policy Compliance plugin version 1.0.5 or lower is installed and any Jenkins job using the plugin has a configurable endpoint that could be set to a malicious server.

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 for Policy Compliance to version 1.0.6 or later, which includes proper permission checks and sanitization of endpoint responses to prevent XXE attacks. Review existing job configurations for any unauthorized endpoint settings.

Recommended fix Moderate confidence

Latest version available in Jenkins Plugin Repository (version > 1.0.5)

  1. Navigate to the Jenkins dashboard and go to Manage Jenkins
  2. Access Manage Plugins and locate the Qualys Plugin for Policy Compliance
  3. Check the currently installed version to confirm it is 1.0.5 or lower
  4. Upgrade the plugin to the latest available version from the Jenkins Plugin Repository
  5. After upgrade, verify the new version is installed and restart Jenkins if required
  6. Review any configuration changes needed in job configurations that use the Qualys Policy Compliance plugin
Caveat Review release notes for any configuration or behavior changes between 1.0.5 and the target version

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

Fix this in Policy Compliance Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
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,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-6147 — 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-6147 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