CVE-2024-29030 is a medium-severity (CVSS 5.8) Server-Side Request Forgery (SSRF) vulnerability in github.com/usememos/memos. A fix is available for github.com/usememos/memos — see the affected versions and patch details below.
memos vulnerable to an SSRF in /api/resource
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-29030.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/usememos/memosReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/usememos/memos | all versions | 0.22.0go get github.com/usememos/memos@v0.22.0 |
Affected Products
memosusememosDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/usememos/memos, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/usememos/memos to 0.22.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-29030 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.
How to detect CVE-2024-29030
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id cve-2024-29030 -u https://target- Template
- Memos 0.13.2 - Server-Side Request Forgery
- Severity
- medium
- Impact
- Attackers can force the server to make requests to arbitrary destinations, potentially accessing internal services or sensitive data.
- Remediation
- Update Memos to version 0.13.3 or later.
Template by ProjectDiscovery nuclei-templates (ritikchaddha), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is CVE-2024-29030 in your dependencies?
Find it across Go, including transitive dependencies.