Is CVE-2023-5571 exploited in the wild?

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

How severe is CVE-2023-5571?

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-5571?

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-5571 attacked?

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

Am I affected by CVE-2023-5571?

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-5571: Vrite SDK improper input validation

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

The Vrite SDK is a JavaScript library used by developers to integrate Vrite content management features into applications. A flaw in input validation allows attackers to send malicious or malformed data without proper sanitization, potentially compromising data integrity or causing service disruptions. Organizations using affected versions should upgrade to 0.3.0 or later.

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

Quick answers

Is CVE-2023-5571 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2023-5571 being exploited in the wild.
How severe is CVE-2023-5571?: 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-5571?: 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-5571 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2023-5571?: 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

This vulnerability is classified as improper input validation (CWE-20) in the @vrite/sdk library affecting all versions prior to 0.3.0. The root cause involves insufficient validation of user-supplied input data, allowing attackers to send requests with unexpected or malicious payloads that bypass safety checks. The vulnerability is network-accessible and requires no authentication or special privileges. An attacker can exploit this to corrupt data, cause integrity issues, or trigger denial of service conditions. The fix was implemented in version 0.3.0 as documented in commit 1877683b932bb33fb20d688e476284b70bb9fe23, which restructured the backend and tightened CORS API access controls.

Affected products

Vrite @vrite/sdk <0.3.0

Identifiers

CVE-2023-5571
GHSA-44ff-9w4f-99w6

Timeline

2023-10-13: disclosed: Vulnerability published on GitHub Security Advisory
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.