ghsa-c76h-2ccp-4975
Vulnerability from github
Published
2025-01-21 21:10
Modified
2025-01-21 21:10
Severity ?
6.8 (Medium) - CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
Summary
Use of Insufficiently Random Values in undici
Details

Impact

Undici fetch() uses Math.random() to choose the boundary for a multipart/form-data request. It is known that the output of Math.random() can be predicted if several of its generated values are known.

If there is a mechanism in an app that sends multipart requests to an attacker-controlled website, they can use this to leak the necessary values. Therefore, An attacker can tamper with the requests going to the backend APIs if certain conditions are met.

Patches

This is fixed in 5.28.5; 6.21.1; 7.2.3.

Workarounds

Do not issue multipart requests to attacker controlled servers.

References

  • https://hackerone.com/reports/2913312
  • https://blog.securityevaluators.com/hacking-the-javascript-lottery-80cc437e3b7f
Show details on source website

To clipboard 

{
   affected: [
      {
         package: {
            ecosystem: "npm",
            name: "undici",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "4.5.0",
                  },
                  {
                     fixed: "5.28.5",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
      {
         package: {
            ecosystem: "npm",
            name: "undici",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "6.0.0",
                  },
                  {
                     fixed: "6.21.1",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
      {
         package: {
            ecosystem: "npm",
            name: "undici",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "7.0.0",
                  },
                  {
                     fixed: "7.2.3",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
   ],
   aliases: [
      "CVE-2025-22150",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-330",
      ],
      github_reviewed: true,
      github_reviewed_at: "2025-01-21T21:10:47Z",
      nvd_published_at: "2025-01-21T18:15:14Z",
      severity: "MODERATE",
   },
   details: "### Impact\n\n[Undici `fetch()` uses Math.random()](https://github.com/nodejs/undici/blob/8b06b8250907d92fead664b3368f1d2aa27c1f35/lib/web/fetch/body.js#L113) to choose the boundary for a multipart/form-data request. It is known that the output of Math.random() can be predicted if several of its generated values are known.\n\nIf there is a mechanism in an app that sends multipart requests to an attacker-controlled website, they can use this to leak the necessary values. Therefore, An attacker can tamper with the requests going to the backend APIs if certain conditions are met.\n\n### Patches\n\nThis is fixed in 5.28.5; 6.21.1; 7.2.3.\n\n### Workarounds\n\nDo not issue multipart requests to attacker controlled servers.\n\n### References\n\n* https://hackerone.com/reports/2913312\n* https://blog.securityevaluators.com/hacking-the-javascript-lottery-80cc437e3b7f\n",
   id: "GHSA-c76h-2ccp-4975",
   modified: "2025-01-21T21:10:47Z",
   published: "2025-01-21T21:10:47Z",
   references: [
      {
         type: "WEB",
         url: "https://github.com/nodejs/undici/security/advisories/GHSA-c76h-2ccp-4975",
      },
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2025-22150",
      },
      {
         type: "WEB",
         url: "https://github.com/nodejs/undici/commit/711e20772764c29f6622ddc937c63b6eefdf07d0",
      },
      {
         type: "WEB",
         url: "https://github.com/nodejs/undici/commit/c2d78cd19fe4f4c621424491e26ce299e65e934a",
      },
      {
         type: "WEB",
         url: "https://github.com/nodejs/undici/commit/c3acc6050b781b827d80c86cbbab34f14458d385",
      },
      {
         type: "WEB",
         url: "https://hackerone.com/reports/2913312",
      },
      {
         type: "WEB",
         url: "https://blog.securityevaluators.com/hacking-the-javascript-lottery-80cc437e3b7f",
      },
      {
         type: "PACKAGE",
         url: "https://github.com/nodejs/undici",
      },
      {
         type: "WEB",
         url: "https://github.com/nodejs/undici/blob/8b06b8250907d92fead664b3368f1d2aa27c1f35/lib/web/fetch/body.js#L113",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N",
         type: "CVSS_V3",
      },
   ],
   summary: "Use of Insufficiently Random Values in undici",
}


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.