CVE-2023-5573: Allocation of Resources Without Limits or Throttling in @vrite/sdk

@vrite/sdk Updated 02 Oct 2025

Summary

13/10/2023
Yes i
Moderate
4.7

CVE-2023-5573: Allocation of Resources Without Limits or Throttling in vriteio/vrite. Affects @vrite/sdk versions < 0.3.0. Fixed in 0.3.0. 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

The @vrite/sdk package is an npm package that is part of the vriteio/vrite GitHub repository. It provides functionality for interacting with the vrite platform. The package allows users to allocate resources and perform various operations within the vrite ecosystem. However, prior to version 0.3.0, the package is vulnerable to an issue that allows the allocation of resources without any limits or throttling.

Vulnerability Detail

The vulnerability in @vrite/sdk allows for the allocation of resources without any limits or throttling. This means that an attacker or a malicious user can abuse the package to consume excessive resources, potentially leading to resource exhaustion and denial of service. The lack of resource limits or throttling can also impact the stability and performance of the vrite platform. The vulnerability has a CVSS score of 4.7, indicating a moderate severity level.

How To Fix

Minimum fixed version

0.3.0

This is the first release that contains the fix.

npm install @vrite/sdk@0.3.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Conclusion

In conclusion, the @vrite/sdk package prior to version 0.3.0 is vulnerable to the allocation of resources without limits or throttling. This can lead to resource exhaustion, denial of service, and impact the stability of the vrite platform. To fix the vulnerability, it is recommended to upgrade to version 0.3.0 or later of the package. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for @vrite/sdk →

Share this vulnerability

FAQ

The vulnerability allows for the allocation of resources without any limits or throttling, which can lead to resource exhaustion and denial of service. It can also impact the stability and performance of the vrite platform.

Yes, the vulnerability can be fixed by upgrading to version 0.3.0 or later of the @vrite/sdk package.

You can update the package by running the following command: npm install @vrite/sdk@0.3.0

No, there are no known workarounds for this vulnerability. It is recommended to upgrade to the fixed version of the package.

You can find more information about this vulnerability in the GitHub advisory database: [link to advisory]

Related vulnerabilities

Recent vulnerabilities recorded for @vrite/sdk.

How To Fix

Minimum fixed version

0.3.0

This is the first release that contains the fix.

npm install @vrite/sdk@0.3.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. 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