How severe is GHSA-qrrf-xvcf-p64q?

GHSA-qrrf-xvcf-p64q has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-qrrf-xvcf-p64q?

GHSA-qrrf-xvcf-p64q affects the following packages: github.com/usememos/memos (Go). Ecosystems affected: Go.

How do I fix GHSA-qrrf-xvcf-p64q?

Update github.com/usememos/memos to 0.9.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qrrf-xvcf-p64q is resolved across your whole dependency graph.

How do I detect GHSA-qrrf-xvcf-p64q in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/usememos/memos. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-qrrf-xvcf-p64q if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-qrrf-xvcf-p64q?

O3 pinpoints whether GHSA-qrrf-xvcf-p64q is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-qrrf-xvcf-p64q actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-qrrf-xvcf-p64q, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What type of vulnerability is GHSA-qrrf-xvcf-p64q?

GHSA-qrrf-xvcf-p64q is classified as CWE-307 (CWE-307). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-qrrf-xvcf-p64q published, and has it been updated?

GHSA-qrrf-xvcf-p64q was published on December 28, 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

GHSA-qrrf-xvcf-p64q

MEDIUM

GHSA-qrrf-xvcf-p64q is a medium-severity (CVSS 4.3) CWE-307 vulnerability in github.com/usememos/memos. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-qrrf-xvcf-p64q is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

usememos/memos vulnerable Improper Restriction of Excessive Authentication Attempts

Also known asCVE-2022-4797GO-2022-1244

Published

Dec 28, 2022

Updated

Aug 21, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Blast Radius

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

In usememos/memos 0.9.0 and prior, an attacker can delete other users' posts via post id, which can be done via brute force.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/usememos/memos`	all versions	0.9.1

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Improper Restriction of Excessive Authentication Attempts in GitHub repo…

huntr.devNVDJan 2023

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/usememos/memos to 0.9.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qrrf-xvcf-p64q is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-qrrf-xvcf-p64q is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-qrrf-xvcf-p64q. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In usememos/memos 0.9.0 and prior, an attacker can delete other users' posts via post id, which can be done via brute force.

O3 Security · Impact-Aware SCA

Is GHSA-qrrf-xvcf-p64q in your dependencies?

O3 detects GHSA-qrrf-xvcf-p64q across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works