CVE-2024-25355: s3-url-parser Denial of Service via regexes component

s3-url-parser Updated 02 Oct 2025

Summary

01/05/2024
No i
High
7.5

CVE-2024-25355: s3-url-parser vulnerable to Denial of Service via regexes component. Affects s3-url-parser versions 1.0.3. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

s3-url-parser is an npm package used for parsing and manipulating URLs related to Amazon S3. It provides functionality to extract information such as bucket name, object key, and region from S3 URLs. The package is widely used in applications that interact with Amazon S3 for storage and retrieval of objects. However, version 1.0.3 of s3-url-parser is vulnerable to a denial of service attack due to a flaw in the regexes component.

Vulnerability Detail

The vulnerability in s3-url-parser version 1.0.3 allows an attacker to trigger a denial of service attack by exploiting the regexes component. By sending a specially crafted URL, the regular expressions used for parsing the URL can be manipulated to cause excessive backtracking, leading to high CPU usage and unresponsiveness of the application. This can result in a complete denial of service, rendering the application unavailable to legitimate users.

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

As a temporary workaround, developers can implement input validation and sanitization to mitigate the risk of exploitation. By validating and sanitizing user-supplied URLs before passing them to s3-url-parser, the impact of the vulnerability can be reduced. This can be achieved by using libraries or built-in functions that enforce strict URL validation and reject malicious inputs.

Conclusion

s3-url-parser version 1.0.3 is vulnerable to a denial of service attack due to a flaw in the regexes component. To mitigate this vulnerability, it is crucial to upgrade to a patched version of the package and regularly update dependencies. Implementing input validation and sanitization can provide temporary protection. For further assistance or support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for s3-url-parser →

Share this vulnerability

FAQ

The vulnerability allows an attacker to launch a denial of service attack, causing the affected application to become unresponsive and unavailable to legitimate users.

You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. The playground analyzes your package-lock.json file and provides real-time alerts for open-source vulnerabilities, including this one.

At the time of this advisory, there are no known public exploits specifically targeting this vulnerability. However, it is important to apply the recommended fix to prevent any potential exploitation.

No, a CVSS score has not been assigned to this vulnerability at the moment. It is advisable to follow the recommended remediation steps provided in this advisory.

While upgrading to a patched version is the recommended approach, you can mitigate the risk by implementing input validation and sanitization for user-supplied URLs. This can help reduce the impact of the vulnerability until the package is updated.

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