# GHSA-rrqv-vjrw-hrcr: Arbitrary Code Execution in json-ptr

> Attackers can execute arbitrary code by sending unsanitized input to the json-ptr library's get method, requiring developers to upgrade the package.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 May 2021

## What is GHSA-rrqv-vjrw-hrcr?

GHSA-rrqv-vjrw-hrcr is a code injection vulnerability in json-ptr, published on 26 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

There is a security vulnerability in `json-ptr` versions prior to v2.1.0 in which an unscrupulous actor may execute arbitrary code. If your code sends un-sanitized user input to json-ptr's .get() method, your project is vulnerable to this injection-style vulnerability.

## Which versions are affected by GHSA-rrqv-vjrw-hrcr?

2 open source packages ship an affected version, including json-ptr.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `json-ptr` | npm | All versions | 2.1.0 |
| `json-ptr` | npm | All versions | 2.1.0 |

## How do I fix GHSA-rrqv-vjrw-hrcr?

Upgrade json-ptr to 2.1.0 or later.

## Is GHSA-rrqv-vjrw-hrcr being exploited?

There is no known exploitation of GHSA-rrqv-vjrw-hrcr in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-rrqv-vjrw-hrcr and fix it if it is affected.

What it is: GHSA-rrqv-vjrw-hrcr is a code injection vulnerability in json-ptr, published on 26 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-rrqv-vjrw-hrcr in the wild and no public exploit code.

Affected packages and fixed versions:
- json-ptr (npm): affected all versions; fixed in 2.1.0
- json-ptr (npm): affected all versions; fixed in 2.1.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-rrqv-vjrw-hrcr/ (Markdown: https://insights.sbomify.com/GHSA-rrqv-vjrw-hrcr/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-rrqv-vjrw-hrcr

---
From sbomify Insights: https://insights.sbomify.com/GHSA-rrqv-vjrw-hrcr/
Summaries are generated and may contain mistakes; the official description above is the record.