# CVE-2022-46383: Information disclosure in n/a

> An attacker can obtain a privileged token from a public API endpoint to escalate privileges and gain full administrative access to the Digital Rebar system.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Dec 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-gvwr-2f69-3xgr

## What is CVE-2022-46383?

CVE-2022-46383 is a critical vulnerability in n/a, published on 6 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

RackN Digital Rebar through 4.6.14, 4.7 through 4.7.22, 4.8 through 4.8.5, 4.9 through 4.9.12, and 4.10 through 4.10.8 has exposed a privileged token via a public API endpoint (Incorrect Access Control). The token can be used to escalate privileges within the Digital Rebar system and grant full administrative access.

## Which versions are affected by CVE-2022-46383?

It affects 1 product.


Products: Rackn Digital Rebar.

## How do I fix CVE-2022-46383?

No fix has been published for CVE-2022-46383 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-46383 being exploited?

There is no known exploitation of CVE-2022-46383 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2022-46382](https://insights.sbomify.com/CVE-2022-46382/): Auth bypass in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-46383 and fix it if it is affected.

What it is: CVE-2022-46383 is a critical vulnerability in n/a, published on 6 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-46383 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/CVE-2022-46383/ (Markdown: https://insights.sbomify.com/CVE-2022-46383/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-46383
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-46383
- OSV: https://osv.dev/vulnerability/CVE-2022-46383

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-46383/
Summaries are generated and may contain mistakes; the official description above is the record.