ghsa-8525-52vg-jv6v
Vulnerability from github
Published
2024-01-09 09:30
Modified
2024-01-12 22:32
Severity ?
5.7 (Medium) - CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
Summary
Qualys Jenkins Plugin for Policy Compliance XML External Entity vulnerability
Details

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

Show details on source website

To clipboard 

{
   affected: [
      {
         database_specific: {
            last_known_affected_version_range: "<= 1.0.5",
         },
         package: {
            ecosystem: "Maven",
            name: "com.qualys.plugins:qualys-pc",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "0",
                  },
                  {
                     fixed: "1.0.6",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
   ],
   aliases: [
      "CVE-2023-6147",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-611",
      ],
      github_reviewed: true,
      github_reviewed_at: "2024-01-09T18:50:03Z",
      nvd_published_at: "2024-01-09T08:15:36Z",
      severity: "MODERATE",
   },
   details: "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",
   id: "GHSA-8525-52vg-jv6v",
   modified: "2024-01-12T22:32:30Z",
   published: "2024-01-09T09:30:29Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2023-6147",
      },
      {
         type: "PACKAGE",
         url: "https://github.com/jenkinsci/qualys-pc-plugin",
      },
      {
         type: "WEB",
         url: "https://plugins.jenkins.io/qualys-pc",
      },
      {
         type: "WEB",
         url: "https://www.qualys.com/security-advisories",
      },
      {
         type: "WEB",
         url: "https://www.qualys.com/security-advisories/cve-2023-6147",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2024/01/24/6",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N",
         type: "CVSS_V3",
      },
   ],
   summary: "Qualys Jenkins Plugin for Policy Compliance XML External Entity vulnerability",
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.