Usememos Memos vulnerabilities, page 3

78 vulnerabilities

Known vulnerabilities in Usememos Memos, newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.

9.8CVE-2022-4851github.com/usememosmemos+2
EPSS score
0.79%
Improper Handling of Values in GitHub repository usememos/memos prior to 0.9.1.
8.6CVE-2022-4841github.com/usememosmemos+2
EPSS score
0.62%
Cross-site Scripting (XSS) - Stored in GitHub repository usememos/memos prior to 0.9.1.
7.1CVE-2022-4690github.com/usememosmemos+2
EPSS score
0.62%
Cross-site Scripting (XSS) - Stored in GitHub repository usememos/memos prior to 0.9.0.
8.2CVE-2022-4807github.com/usememosmemos+2
EPSS score
0.59%
Improper Access Control in GitHub repository usememos/memos prior to 0.9.1.
5.7CVE-2022-4694github.com/usememosmemos+2
EPSS score
0.56%
Cross-site Scripting (XSS) - Stored in GitHub repository usememos/memos prior to 0.9.0.
8.6CVE-2022-4848github.com/usememosmemos+2
EPSS score
0.54%
Improper Verification of Source of a Communication Channel in GitHub repository usememos/memos prior to 0.9.1.
7.3CVE-2022-4805github.com/usememosmemos+2
EPSS score
0.52%
Incorrect Use of Privileged APIs in GitHub repository usememos/memos prior to 0.9.1.
8.4CVE-2022-4863github.com/usememosmemos+2
EPSS score
0.70%
Improper Handling of Insufficient Permissions or Privileges in GitHub repository usememos/memos prior to 0.9.1.
6.5CVE-2022-4850github.com/usememosmemos+2
EPSS score
0.34%
Cross-Site Request Forgery (CSRF) in GitHub repository usememos/memos prior to 0.9.1.
8.3CVE-2022-4849github.com/usememosmemos+2
EPSS score
0.36%
Cross-Site Request Forgery (CSRF) in GitHub repository usememos/memos prior to 0.9.1.
6.5CVE-2022-4846github.com/usememosmemos+2
EPSS score
0.26%
Cross-Site Request Forgery (CSRF) in GitHub repository usememos/memos prior to 0.9.1.
8.6CVE-2022-4812github.com/usememosmemos+2
EPSS score
0.59%
Authorization Bypass Through User-Controlled Key in GitHub repository usememos/memos prior to 0.9.1.
9.8CVE-2022-4797github.com/usememosmemos+2
EPSS score
0.73%
Improper Restriction of Excessive Authentication Attempts in GitHub repository usememos/memos prior to 0.9.1.
8.6CVE-2022-4798github.com/usememosmemos+2
EPSS score
0.72%
Authorization Bypass Through User-Controlled Key in GitHub repository usememos/memos prior to 0.9.1.
9.8CVE-2022-4866github.com/usememosmemos+2
EPSS score
1.02%
Cross-site Scripting (XSS) - Stored in GitHub repository usememos/memos prior to 0.9.1.
9.8CVE-2022-4686github.com/usememosmemos+2
EPSS score
0.75%
Authorization Bypass Through User-Controlled Key in GitHub repository usememos/memos prior to 0.9.0.
7.6CVE-2022-4767github.com/usememosmemos+2
EPSS score
0.70%
Denial of Service in GitHub repository usememos/memos prior to 0.9.1.
7.5CVE-2024-21635github.com/usememosmemos+1
EPSS score
0.31%
Memos is a privacy-first, lightweight note-taking service that uses Access Tokens to authenticate application access. When a user changes their password, the existing list of Access Tokens stay valid instead of expiring. If a user finds that their account has been compromised, they can update their password. In versions up to and including 0.18.1, though, the bad actor will still have access to their account because the bad actor's Access Token stays on the list as a valid token. The user will have to manually delete the bad actor's Access Token to secure their account. The list of Access Tokens has a generic Description which makes it hard to pinpoint a bad actor in a list of Access Tokens. A known patched version of Memos isn't available. To improve Memos security, all Access Tokens will need to be revoked when a user changes their password. This removes the session for all the user's devices and prompts the user to log in again. One can treat the old Access Tokens as "invalid" because those Access Tokens were created with the older password.
8.1CVE-2024-41659github.com/usememosmemos+1
EPSS score
0.64%
memos is a privacy-first, lightweight note-taking service. A CORS misconfiguration exists in memos 0.20.1 and earlier where an arbitrary origin is reflected with Access-Control-Allow-Credentials set to true. This may allow an attacking website to make a cross-origin request, allowing the attacker to read private information or make privileged changes to the system as the vulnerable user account. This vulnerability is fixed in 0.21.0.
5.8CVE-2024-29030github.com/usememosmemos+1
EPSS score
1.14%
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.