GHSA-qgc4-8p88-4w7m

Suggest an improvement
Source
https://github.com/advisories/GHSA-qgc4-8p88-4w7m
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2025/12/GHSA-qgc4-8p88-4w7m/GHSA-qgc4-8p88-4w7m.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-qgc4-8p88-4w7m
Aliases
Published
2025-12-11T18:36:54Z
Modified
2025-12-12T16:19:25.656381Z
Severity
  • 8.7 (High) CVSS_V4 - 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 CVSS Calculator
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

Database specific
{
    "github_reviewed": true,
    "severity": "HIGH",
    "nvd_published_at": "2025-12-12T08:15:48Z",
    "cwe_ids": [
        "CWE-770"
    ],
    "github_reviewed_at": "2025-12-11T18:36:54Z"
}
References

Affected packages

npm / servify-express

Package

Affected ranges

Type
SEMVER
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
1.2

Database specific

last_known_affected_version_range
"<= 1.1"
source
"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2025/12/GHSA-qgc4-8p88-4w7m/GHSA-qgc4-8p88-4w7m.json"