ghsa-qgc4-8p88-4w7m
Vulnerability from github
Published
2025-12-11 18:36
Modified
2025-12-12 16:12
Severity ?
8.7 (High) - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Summary
Servify-express rate limit issue
Details

Impact

The Express server uses express.json() without a size limit, which can allow attackers to send extremely large request bodies. This may lead to excessive memory usage, degraded performance, or process crashes, resulting in a Denial of Service (DoS). Any application using the JSON parser without limits and exposed to untrusted clients is affected.

Patches

This issue is not a flaw in Express itself but in configuration. Users should set a request-size limit when enabling the JSON body parser. For example: app.use(express.json({ limit: "100kb" }));

Workarounds

Users can mitigate the issue without upgrading by: - Adding a limit option to the JSON parser - Implementing rate limiting at the application or reverse-proxy level - Rejecting unusually large requests before parsing - Using a reverse proxy (such as NGINX) to enforce maximum request body sizes

Show details on source website

To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 1.1"
      },
      "package": {
        "ecosystem": "npm",
        "name": "servify-express"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2025-67731"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-770"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2025-12-11T18:36:54Z",
    "nvd_published_at": "2025-12-12T08:15:48Z",
    "severity": "HIGH"
  },
  "details": "### Impact\nThe Express server uses `express.json()` without a size limit, which can allow attackers to send extremely large request bodies. This may lead to excessive memory usage, degraded performance, or process crashes, resulting in a Denial of Service (DoS). Any application using the JSON parser without limits and exposed to untrusted clients is affected.\n\n### Patches\nThis issue is not a flaw in Express itself but in configuration. Users should set a request-size limit when enabling the JSON body parser. For example:\n`app.use(express.json({ limit: \"100kb\" }));`\n\n### Workarounds\nUsers can mitigate the issue without upgrading by:\n- Adding a `limit` option to the JSON parser\n- Implementing rate limiting at the application or reverse-proxy level\n- Rejecting unusually large requests before parsing\n- Using a reverse proxy (such as NGINX) to enforce maximum request body sizes",
  "id": "GHSA-qgc4-8p88-4w7m",
  "modified": "2025-12-12T16:12:24Z",
  "published": "2025-12-11T18:36:54Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/Aarondoran/servify-express/security/advisories/GHSA-qgc4-8p88-4w7m"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-67731"
    },
    {
      "type": "WEB",
      "url": "https://github.com/Aarondoran/servify-express/commit/197d848e5450bf85b0dd19ef8c2aa4ba96192300"
    },
    {
      "type": "WEB",
      "url": "https://github.com/Aarondoran/servify-express/commit/8dff7f56504b356278d849734ef2050e5cd23b61"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/Aarondoran/servify-express"
    },
    {
      "type": "WEB",
      "url": "https://github.com/Aarondoran/servify-express/releases/tag/V1.2"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "Servify-express rate limit issue"
}


Log in or create an account to share your comment.




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.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • 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.