# CVE-2024-29030: memos vulnerable to an SSRF in /api/resource

> Authenticated users can exploit an SSRF vulnerability in the /api/resource endpoint to enumerate the internal network.

- **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-65fm-2jgr-j7qq, GO-2024-3046

## What is CVE-2024-29030?

CVE-2024-29030 is a medium-severity server-side request forgery vulnerability in Usememos Memos, published on 19 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

memos is a privacy-first, lightweight note-taking service. In memos 0.13.2, an SSRF vulnerability exists at the /api/resource that allows authenticated users to enumerate the internal network. Version 0.22.0 of memos removes the vulnerable file.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2024-29030?

3 open source packages ship an affected version, including github.com/usememos/memos. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/usememos/memos` | Go | All versions | 0.22.0 |
| `github.com/usememos/memos` | Go | All versions | 0.22.0 |
| `github.com/usememos/memos` | Go | All versions | 0.22.0 |

Products: Usememos Memos.

## How do I fix CVE-2024-29030?

Upgrade github.com/usememos/memos to 0.22.0 or later.

## Is CVE-2024-29030 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-29030 exists.

Public exploit code:

- Memos 0.13.2 - Server-Side Request Forgery (nuclei): http/cves/2024/CVE-2024-29030.yaml

## Other vulnerabilities in Usememos Memos

- [CVE-2025-50738](https://insights.sbomify.com/CVE-2025-50738/): Memos has Cross-Site Scripting (XSS) Vulnerability in Image URLs (critical 9.8)
- [CVE-2025-22952](https://insights.sbomify.com/CVE-2025-22952/): Memos Server-Side Request Forgery (SSRF) (critical 9.8)
- [CVE-2023-0109](https://insights.sbomify.com/CVE-2023-0109/): Stored XSS in usememos/memos (critical 9.8)
- [CVE-2023-4696](https://insights.sbomify.com/CVE-2023-4696/): Improper Access Control in usememos/memos (critical 9.8)
- [CVE-2022-4866](https://insights.sbomify.com/CVE-2022-4866/): Cross-site Scripting (XSS) - Stored in usememos/memos (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-29030 and fix it if it is affected.

What it is: CVE-2024-29030 is a medium-severity server-side request forgery vulnerability in Usememos Memos, published on 19 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-29030 exists.

Affected packages and fixed versions:
- github.com/usememos/memos (Go): affected all versions; fixed in 0.22.0
- github.com/usememos/memos (Go): affected all versions; fixed in 0.22.0
- github.com/usememos/memos (Go): affected all versions; fixed in 0.22.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/CVE-2024-29030/ (Markdown: https://insights.sbomify.com/CVE-2024-29030/index.md)
```

## Sources

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

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