Skip to content

usememos/memos Incorrect Use of Privileged APIs vulnerability

Moderate severity GitHub Reviewed Published Dec 28, 2022 to the GitHub Advisory Database • Updated Feb 3, 2023

Package

gomod github.com/usememos/memos (Go)

Affected versions

<= 0.9.0

Patched versions

0.9.1

Description

In usememos/memos 0.9.0 and prior, a user can archive any private memos, delete any shortcut, and edit any shortcut from other users via API.

References

Published by the National Vulnerability Database Dec 28, 2022
Published to the GitHub Advisory Database Dec 28, 2022
Reviewed Dec 30, 2022
Last updated Feb 3, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

EPSS score

0.053%
(23rd percentile)

Weaknesses

CVE ID

CVE-2022-4805

GHSA ID

GHSA-mq5q-gpgv-pwxw

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.