ghsa-p34j-r3ch-c985
Vulnerability from github
Published
2025-03-06 00:31
Modified
2025-03-06 22:30
Summary
Jenkins reveals encrypted values of secrets stored in agent configuration to users with Agent/Extended Read permission
Details

Jenkins 2.499 and earlier, LTS 2.492.1 and earlier does not redact encrypted values of secrets when accessing config.xml of agents via REST API or CLI.

This allows attackers with Agent/Extended Read permission to view encrypted values of secrets.

Jenkins 2.500, LTS 2.492.2 redacts the encrypted values of secrets stored in agent config.xml accessed via REST API or CLI for users lacking Agent/Configure permission.

Show details on source website


{
   affected: [
      {
         package: {
            ecosystem: "Maven",
            name: "org.jenkins-ci.main:jenkins-core",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "2.493",
                  },
                  {
                     fixed: "2.500",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
      {
         package: {
            ecosystem: "Maven",
            name: "org.jenkins-ci.main:jenkins-core",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "0",
                  },
                  {
                     fixed: "2.492.2",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
   ],
   aliases: [
      "CVE-2025-27622",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-312",
      ],
      github_reviewed: true,
      github_reviewed_at: "2025-03-06T22:30:07Z",
      nvd_published_at: "2025-03-05T23:15:13Z",
      severity: "MODERATE",
   },
   details: "Jenkins 2.499 and earlier, LTS 2.492.1 and earlier does not redact encrypted values of secrets when accessing `config.xml` of agents via REST API or CLI.\n\nThis allows attackers with Agent/Extended Read permission to view encrypted values of secrets.\n\nJenkins 2.500, LTS 2.492.2 redacts the encrypted values of secrets stored in agent `config.xml` accessed via REST API or CLI for users lacking Agent/Configure permission.",
   id: "GHSA-p34j-r3ch-c985",
   modified: "2025-03-06T22:30:08Z",
   published: "2025-03-06T00:31:56Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2025-27622",
      },
      {
         type: "WEB",
         url: "https://github.com/jenkinsci/jenkins/commit/923cdbc165e8b8523ae960dfee5f7354878532d5",
      },
      {
         type: "PACKAGE",
         url: "https://github.com/jenkinsci/jenkins",
      },
      {
         type: "WEB",
         url: "https://www.jenkins.io/security/advisory/2025-03-05/#SECURITY-3495",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
         type: "CVSS_V3",
      },
   ],
   summary: "Jenkins reveals encrypted values of secrets stored in agent configuration to users with Agent/Extended Read permission",
}


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.


Loading…

Loading…

Loading…

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.