How severe is CVE-2022-4685?

No CVSS score has been assigned to CVE-2022-4685 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2022-4685?

CVE-2022-4685 affects the following packages: github.com/usememos/memos (Go). Ecosystems affected: Go.

How do I fix CVE-2022-4685?

Update github.com/usememos/memos to 0.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-4685 is resolved across your whole dependency graph.

How do I detect CVE-2022-4685 in my Go dependencies?

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.

How do I mitigate CVE-2022-4685 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2022-4685 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-4685 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was CVE-2022-4685 published, and has it been updated?

CVE-2022-4685 was published on December 23, 2022 and was last updated on August 21, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CVE-2022-4685 — memos

Fix: usememos/memos@dca35bd

CVE-2022-4685 is a security vulnerability in github.com/usememos/memos. A fix is available for github.com/usememos/memos — see the affected versions and patch details below.

usememos/memos vulnerable to improper access control

Also known asGO-2022-1205

Published

Dec 23, 2022

Updated

Aug 21, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 21, 2024 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹github.com/usememos/memos

Real-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

Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. Reason: This CVE has been rejected as it was incorrectly assigned. All references and descriptions in this candidate have been removed to prevent accidental usage.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/usememos/memos`	all versions	0.9.0`go get github.com/usememos/memos@v0.9.0`

Detection & mitigation playbook

Open-source dependency

Detect
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.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-4685 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

Improper Access Control in GitHub repository usememos/memos prior to 0.9.0.

O3 Security · Impact-Aware SCA

Is CVE-2022-4685 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works