# CVE-2023-49946: Missing authorization in n/a

> Remote attackers can read private issues and pull requests or delete issues due to missing object ownership checks in Forgejo.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-fv68-mgcx-47jh

## What is CVE-2023-49946?

CVE-2023-49946 is a critical missing authorization vulnerability in n/a, published on 3 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Forgejo before 1.20.5-1, certain endpoints do not check whether an object belongs to a repository for which permissions are being checked. This allows remote attackers to read private issues, read private pull requests, delete issues, and perform other unauthorized actions.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2023-49946?

It affects 1 product.


Products: Forgejo Forgejo.

## How do I fix CVE-2023-49946?

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

## Is CVE-2023-49946 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-49947](https://insights.sbomify.com/CVE-2023-49947/): Auth bypass in n/a (high 7.5)
- [CVE-2023-49948](https://insights.sbomify.com/CVE-2023-49948/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-49946 and fix it if it is affected.

What it is: CVE-2023-49946 is a critical missing authorization vulnerability in n/a, published on 3 Dec 2023. 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-2023-49946 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-2023-49946/ (Markdown: https://insights.sbomify.com/CVE-2023-49946/index.md)
```

## Sources

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

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