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

> Attackers can access audit logs without proper authorization due to mishandled ACLs in MISP.

- **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:** 15 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-mh7x-8j8h-xvj8

## What is CVE-2023-50918?

CVE-2023-50918 is a critical missing authorization vulnerability in Misp-Project Misp, published on 15 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

app/Controller/AuditLogsController.php in MISP before 2.4.182 mishandles ACLs for audit logs.

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

It affects 1 product.


Products: Misp-Project Misp.

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

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

## Is CVE-2023-50918 being exploited?

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

## Other vulnerabilities in Misp-Project Misp

- [CVE-2024-46918](https://insights.sbomify.com/CVE-2024-46918/): Missing authorization in n/a (critical 9.8)
- [CVE-2024-45509](https://insights.sbomify.com/CVE-2024-45509/): Missing authorization in n/a (critical 9.8)
- [CVE-2024-29858](https://insights.sbomify.com/CVE-2024-29858/): File upload in n/a (critical 9.8)
- [CVE-2024-29859](https://insights.sbomify.com/CVE-2024-29859/): File upload in n/a (critical 9.8)
- [CVE-2024-25674](https://insights.sbomify.com/CVE-2024-25674/): File upload in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-50918 is a critical missing authorization vulnerability in Misp-Project Misp, published on 15 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-50918 in the wild and no public exploit code.

Affected product: Misp-Project Misp. 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-50918/ (Markdown: https://insights.sbomify.com/CVE-2023-50918/index.md)
```

## Sources

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

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