# CVE-2022-30852: Known v1.3.1 contains Insecure Direct Object Reference

> An Insecure Direct Object Reference vulnerability allows attackers to access or modify unauthorized data by manipulating object identifiers.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-4v4p-87m3-5423

## What is CVE-2022-30852?

CVE-2022-30852 is a medium-severity missing authorization vulnerability in n/a, published on 8 Jul 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Known v1.3.1 was discovered to contain an Insecure Direct Object Reference (IDOR).

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

2 open source packages ship an affected version, including idno/known. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `idno/known` | Packagist | All versions to 1.3.1 | None |
| `idno/known` | Packagist | All versions to 1.3.1 | None |

Products: Withknown Known.

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

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

## Is CVE-2022-30852 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-26273](https://insights.sbomify.com/CVE-2026-26273/): Known affected by Account Takeover via Password Reset Token Leakage (critical 9.8)
- [CVE-2026-28508](https://insights.sbomify.com/CVE-2026-28508/): Idno: Unauthenticated SSRF via URL Unfurl Endpoint (critical 9.2)
- [CVE-2022-33011](https://insights.sbomify.com/CVE-2022-33011/): Known vulnerable to account takeover via host header injection attack in v1.3.1 (high 8.8)
- [CVE-2026-28507](https://insights.sbomify.com/CVE-2026-28507/): Idno: Remote Code Execution via Chained Import File Write and Template Path Traversal (high 8.6)
- [CVE-2022-32115](https://insights.sbomify.com/CVE-2022-32115/): Known vulnerable to code execution via SVG file in v1.3.1 (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-30852 is a medium-severity missing authorization vulnerability in n/a, published on 8 Jul 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-30852 in the wild and no public exploit code.

Affected packages and fixed versions:
- idno/known (Packagist): affected all versions up to 1.3.1; no fix listed
- idno/known (Packagist): affected all versions up to 1.3.1; no fix listed

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

## Sources

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

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