ghsa-w2hv-rcqr-2h7r
Vulnerability from github
Published
2022-05-24 17:46
Modified
2022-12-13 16:47
Summary
View name validation bypass in Jenkins
Details

Jenkins 2.286 and earlier, LTS 2.277.1 and earlier does not properly check that a newly created view has an allowed name. When a form to create a view is submitted, the name is included twice in the submission. One instance is validated, but the other instance is used to create the value.

This allows attackers with View/Create permission to create views with invalid or already-used names.

Jenkins 2.287, LTS 2.277.2 uses the same submitted value for validation and view creation.

Show details on source website


{
   affected: [
      {
         package: {
            ecosystem: "Maven",
            name: "org.jenkins-ci.main:jenkins-core",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "0",
                  },
                  {
                     fixed: "2.277.2",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
      {
         database_specific: {
            last_known_affected_version_range: "<= 2.286",
         },
         package: {
            ecosystem: "Maven",
            name: "org.jenkins-ci.main:jenkins-core",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "2.278",
                  },
                  {
                     fixed: "2.287",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
   ],
   aliases: [
      "CVE-2021-21640",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-240",
      ],
      github_reviewed: true,
      github_reviewed_at: "2022-06-23T06:49:47Z",
      nvd_published_at: "2021-04-07T14:15:00Z",
      severity: "MODERATE",
   },
   details: "Jenkins 2.286 and earlier, LTS 2.277.1 and earlier does not properly check that a newly created view has an allowed name. When a form to create a view is submitted, the name is included twice in the submission. One instance is validated, but the other instance is used to create the value.\n\nThis allows attackers with View/Create permission to create views with invalid or already-used names.\n\nJenkins 2.287, LTS 2.277.2 uses the same submitted value for validation and view creation.",
   id: "GHSA-w2hv-rcqr-2h7r",
   modified: "2022-12-13T16:47:01Z",
   published: "2022-05-24T17:46:47Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2021-21640",
      },
      {
         type: "WEB",
         url: "https://github.com/jenkinsci/jenkins/commit/42e2c74049ddf5e0aca1fe6aadc7b24fdabb5494",
      },
      {
         type: "PACKAGE",
         url: "https://github.com/jenkinsci/jenkins",
      },
      {
         type: "WEB",
         url: "https://www.jenkins.io/security/advisory/2021-04-07/#SECURITY-1871",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2021/04/07/2",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N",
         type: "CVSS_V3",
      },
   ],
   summary: "View name validation bypass in Jenkins",
}


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.