gsd-2023-33001
Vulnerability from gsd
Modified
2023-12-13 01:20
Details
Jenkins HashiCorp Vault Plugin 360.v0a_1c04cf807d and earlier does not properly mask (i.e., replace with asterisks) credentials in the build log when push mode for durable task logging is enabled.
Aliases
Aliases
CVE-2023-33001


To clipboard 

{
   GSD: {
      alias: "CVE-2023-33001",
      id: "GSD-2023-33001",
   },
   gsd: {
      metadata: {
         exploitCode: "unknown",
         remediation: "unknown",
         reportConfidence: "confirmed",
         type: "vulnerability",
      },
      osvSchema: {
         aliases: [
            "CVE-2023-33001",
         ],
         details: "Jenkins HashiCorp Vault Plugin 360.v0a_1c04cf807d and earlier does not properly mask (i.e., replace with asterisks) credentials in the build log when push mode for durable task logging is enabled.",
         id: "GSD-2023-33001",
         modified: "2023-12-13T01:20:36.974435Z",
         schema_version: "1.4.0",
      },
   },
   namespaces: {
      "cve.org": {
         CVE_data_meta: {
            ASSIGNER: "jenkinsci-cert@googlegroups.com",
            ID: "CVE-2023-33001",
            STATE: "PUBLIC",
         },
         affects: {
            vendor: {
               vendor_data: [
                  {
                     product: {
                        product_data: [
                           {
                              product_name: "Jenkins HashiCorp Vault Plugin",
                              version: {
                                 version_data: [
                                    {
                                       version_affected: "<=",
                                       version_name: "0",
                                       version_value: "360.v0a_1c04cf807d",
                                    },
                                 ],
                              },
                           },
                        ],
                     },
                     vendor_name: "Jenkins Project",
                  },
               ],
            },
         },
         data_format: "MITRE",
         data_type: "CVE",
         data_version: "4.0",
         description: {
            description_data: [
               {
                  lang: "eng",
                  value: "Jenkins HashiCorp Vault Plugin 360.v0a_1c04cf807d and earlier does not properly mask (i.e., replace with asterisks) credentials in the build log when push mode for durable task logging is enabled.",
               },
            ],
         },
         problemtype: {
            problemtype_data: [
               {
                  description: [
                     {
                        lang: "eng",
                        value: "n/a",
                     },
                  ],
               },
            ],
         },
         references: {
            reference_data: [
               {
                  name: "https://www.jenkins.io/security/advisory/2023-05-16/#SECURITY-3077",
                  refsource: "MISC",
                  url: "https://www.jenkins.io/security/advisory/2023-05-16/#SECURITY-3077",
               },
            ],
         },
      },
      "gitlab.com": {
         advisories: [
            {
               affected_range: "(,360.v0a]",
               affected_versions: "All versions up to 360.v0a",
               cvss_v3: "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
               cwe_ids: [
                  "CWE-1035",
                  "CWE-532",
                  "CWE-937",
               ],
               date: "2023-05-25",
               description: "Jenkins HashiCorp Vault Plugin 360.v0a_1c04cf807d and earlier does not properly mask (i.e., replace with asterisks) credentials in the build log when push mode for durable task logging is enabled.",
               fixed_versions: [],
               identifier: "CVE-2023-33001",
               identifiers: [
                  "GHSA-v3fv-v9m6-26g3",
                  "CVE-2023-33001",
               ],
               not_impacted: "",
               package_slug: "maven/com.datapipe.jenkins.plugins/hashicorp-vault-plugin",
               pubdate: "2023-05-16",
               solution: "Unfortunately, there is no solution available yet.",
               title: "Insertion of Sensitive Information into Log File",
               urls: [
                  "https://nvd.nist.gov/vuln/detail/CVE-2023-33001",
                  "https://www.jenkins.io/security/advisory/2023-05-16/#SECURITY-3077",
                  "https://github.com/advisories/GHSA-v3fv-v9m6-26g3",
               ],
               uuid: "a895344b-25fe-494a-bdea-1b9967d81f58",
            },
         ],
      },
      "nvd.nist.gov": {
         configurations: {
            CVE_data_version: "4.0",
            nodes: [
               {
                  children: [],
                  cpe_match: [
                     {
                        cpe23Uri: "cpe:2.3:a:jenkins:hashicorp_vault:*:*:*:*:*:wordpress:*:*",
                        cpe_name: [],
                        versionEndIncluding: "360.v0a_1c04cf807d",
                        vulnerable: true,
                     },
                  ],
                  operator: "OR",
               },
            ],
         },
         cve: {
            CVE_data_meta: {
               ASSIGNER: "jenkinsci-cert@googlegroups.com",
               ID: "CVE-2023-33001",
            },
            data_format: "MITRE",
            data_type: "CVE",
            data_version: "4.0",
            description: {
               description_data: [
                  {
                     lang: "en",
                     value: "Jenkins HashiCorp Vault Plugin 360.v0a_1c04cf807d and earlier does not properly mask (i.e., replace with asterisks) credentials in the build log when push mode for durable task logging is enabled.",
                  },
               ],
            },
            problemtype: {
               problemtype_data: [
                  {
                     description: [
                        {
                           lang: "en",
                           value: "CWE-532",
                        },
                     ],
                  },
               ],
            },
            references: {
               reference_data: [
                  {
                     name: "https://www.jenkins.io/security/advisory/2023-05-16/#SECURITY-3077",
                     refsource: "MISC",
                     tags: [
                        "Vendor Advisory",
                     ],
                     url: "https://www.jenkins.io/security/advisory/2023-05-16/#SECURITY-3077",
                  },
               ],
            },
         },
         impact: {
            baseMetricV3: {
               cvssV3: {
                  attackComplexity: "LOW",
                  attackVector: "NETWORK",
                  availabilityImpact: "NONE",
                  baseScore: 7.5,
                  baseSeverity: "HIGH",
                  confidentialityImpact: "HIGH",
                  integrityImpact: "NONE",
                  privilegesRequired: "NONE",
                  scope: "UNCHANGED",
                  userInteraction: "NONE",
                  vectorString: "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
                  version: "3.1",
               },
               exploitabilityScore: 3.9,
               impactScore: 3.6,
            },
         },
         lastModifiedDate: "2023-05-25T18:40Z",
         publishedDate: "2023-05-16T17:15Z",
      },
   },
}


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.