Is CVE-2023-5573 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2023-5573 being exploited in the wild.

How severe is CVE-2023-5573?

Low severity, with a CVSS score of 3, published 13 October 2023.

Which products and versions are affected?

@vrite/sdk (npm) SEMVER:introduced=0,fixed=0.3.0.

Is there a fix for CVE-2023-5573?

Yes. @vrite/sdk (npm): upgrade to 0.3.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2023-5573 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2023-5573?

Check whether you run @vrite/sdk (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2023-5573: Vrite SDK resource exhaustion via unbounded allocation

CVE-2023-5573 · Severity: low · CVSS 3 · Published 2023-10-13

Vrite is an open-source content management and editing platform used to create and manage digital documents. Versions prior to 0.3.0 contain a flaw where an authenticated administrator can trigger unbounded resource allocation on the server without any rate limiting or throttling controls. An attacker with admin credentials could exploit this to exhaust server memory or CPU, causing the application to slow down or become unavailable to legitimate users.

Technologies: @vrite/sdk (npm). Vendors: npm.

Quick answers

Is CVE-2023-5573 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2023-5573 being exploited in the wild.
How severe is CVE-2023-5573?: Low severity, with a CVSS score of 3, published 13 October 2023.
Which products and versions are affected?: @vrite/sdk (npm) SEMVER:introduced=0,fixed=0.3.0.
Is there a fix for CVE-2023-5573?: Yes. @vrite/sdk (npm): upgrade to 0.3.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2023-5573 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2023-5573?: Check whether you run @vrite/sdk (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

@vrite/sdk (npm): upgrade to 0.3.0 or later
```
npm install @vrite/sdk@0.3.0
```

Technical details

The vulnerability is classified as CWE-770 (Allocation of Resources Without Limits or Throttling) in the @vrite/sdk npm package. The root cause involves insufficient resource consumption controls in API endpoints accessible to authenticated users with high privileges (administrator role). An attacker with admin-level access can make requests that allocate unbounded resources without hitting rate limits, throttling mechanisms, or resource caps. This enables denial-of-service conditions by exhausting available server resources. The vulnerability was patched in version 0.3.0, as indicated by commit 1877683 which introduced CORS configuration improvements and other architectural changes. No network-level authentication bypass is required; exploitation requires valid admin credentials.

Affected products

Vrite @vrite/sdk before 0.3.0

Identifiers

CVE-2023-5573
GHSA-5ghm-h2wq-g3mh

Timeline

2023-10-13: disclosed: Vulnerability published on GitHub Advisory Database and NVD
2023-10-10: patched: Fix released in version 0.3.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.