Denial of Service in subtext

subtext Updated 02 Oct 2025

Summary

03/09/2020
HIGH
No i
High
Not published

GHSA-5854-jvxx-2cg9: Denial of Service in subtext. Affects subtext versions >= 4.1.0. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

subtext is an npm package that provides utilities for parsing and handling HTTP request payloads. It is used in web applications to process incoming data from clients. However, versions of subtext starting from 4.1.0 are vulnerable to a Denial of Service (DoS) attack. This vulnerability stems from a flaw in the Content-Encoding HTTP header parser, which can be exploited by an attacker to cause the application to throw a system error. If the error is not caught by an unhandled exception handler, the application will exit, resulting in a service shutdown.

Vulnerability Detail

The vulnerability in subtext arises from a weakness in the Content-Encoding HTTP header parser. When the header contains certain invalid values, the parser function throws a system error. Since hapi, the framework used by subtext, rethrows system errors instead of catching expected application errors, the error propagates up the stack. If the application does not have an unhandled exception handler, the error will cause the application to terminate, enabling an attacker to disrupt services. This vulnerability has a high severity rating.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. However, updating to the latest version of subtext is the recommended solution.

Conclusion

The vulnerability in subtext can be exploited to cause a Denial of Service attack, resulting in the shutdown of affected services. To mitigate this vulnerability, it is crucial to update the dependencies of your application to use the latest version of subtext (@hapi/subtext). For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for subtext →

Share this vulnerability

FAQ

subtext is an npm package used for parsing and handling HTTP request payloads in web applications.

The vulnerability allows an attacker to trigger a DoS attack, causing the application to shut down and disrupting services.

Versions of subtext starting from 4.1.0 are vulnerable to this DoS vulnerability.

To fix this vulnerability, update your application's dependencies to use the latest version of subtext (@hapi/subtext).

There is no specific workaround mentioned for this vulnerability. Updating to the latest version of subtext is the recommended solution.

Related vulnerabilities

Recent vulnerabilities recorded for subtext.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback