CVE-2019-10798: Uncontrolled Resource Consumption in rdf-graph-array

rdf-graph-array Updated 02 Oct 2025

Summary

13/04/2021
No i
Moderate
5.3

CVE-2019-10798: Uncontrolled Resource Consumption in rdf-graph-array. Affects rdf-graph-array versions < 0.3.0-rc6. 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

The rdf-graph-array package is an npm package that provides functionality for manipulating JavaScript objects in the context of RDF graphs. It allows users to add and modify properties of RDF graphs using the rdf.Graph.prototype.add method. However, versions up to 0.3.0-rc6 of the package are vulnerable to Prototype Pollution.

Vulnerability Detail

The vulnerability in rdf-graph-array arises from the manipulation of JavaScript objects, leading to Prototype Pollution. The rdf.Graph.prototype.add method can be tricked into adding or modifying properties of Object.prototype. This can result in unexpected behavior and potentially allow an attacker to execute arbitrary code or perform unauthorized actions.

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 known workaround for this vulnerability. It is crucial to update to a patched version of the package as soon as possible.

Conclusion

In conclusion, the rdf-graph-array package up to version 0.3.0-rc6 is vulnerable to Prototype Pollution. It is crucial to update to a patched version of the package to mitigate the risk of arbitrary code execution and unauthorized actions. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for rdf-graph-array →

Share this vulnerability

FAQ

Prototype Pollution is a vulnerability that occurs when an attacker can modify the prototype of an object, leading to unexpected behavior or security issues.

The consequences of this vulnerability can vary depending on the context in which the rdf-graph-array package is used. However, it could potentially allow an attacker to execute arbitrary code, perform unauthorized actions, or manipulate the behavior of the affected application.

At the time of this report, there are no known public exploits specifically targeting this vulnerability. However, it is always recommended to update to the latest patched version to mitigate any potential risks.

No, only versions up to and including 0.3.0-rc6 of the rdf-graph-array package are affected by this vulnerability. It is recommended to update to a version beyond this to ensure the security of your application.

You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply provide your package-lock.json file, and Vulert will analyze it in real-time and alert you if any open-source vulnerabilities, including this one, are detected.

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