CVE-2022-4688
HIGHCVSS 8.8/10EPSS 0.74%
Last modified
CVE-2022-4688 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. Improper Authorization in GitHub repository usememos/memos prior to 0.9.0.. EPSS estimates a 0.74% chance of exploitation in the next 30 days.
Description
Improper Authorization in GitHub repository usememos/memos prior to 0.9.0.
Metrics
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Usememos | Memos | < 0.9.0 |
References
- https://github.com/usememos/memos/commit/dca35bde877aab6e64ef51b52e590b5d48f692f9Patch, Third Party Advisory
- https://huntr.dev/bounties/23856e7e-94ff-4dee-97d0-0cd47e9b8ff6Exploit, Issue Tracking, Patch, Third Party Advisory
- https://github.com/usememos/memos/commit/dca35bde877aab6e64ef51b52e590b5d48f692f9Patch, Third Party Advisory
- https://huntr.dev/bounties/23856e7e-94ff-4dee-97d0-0cd47e9b8ff6Exploit, Issue Tracking, Patch, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2022-4688?
Improper Authorization in GitHub repository usememos/memos prior to 0.9.0.
How severe is CVE-2022-4688?
CVE-2022-4688 has a CVSS score of 8.8/10 (HIGH severity). The EPSS model estimates a 0.74% probability of exploitation in the next 30 days.
How do I fix CVE-2022-4688?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- Uncovering a hidden BOLA in Appsmith's snapshot logicStrix autonomously discovered a BOLA/IDOR vulnerability in Appsmith's snapshot deletion path.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2022
- CVE-2022-46873Because Firefox did not implement the <code>unsafe-hashes</c…8.8
- CVE-2022-46874A file with a long filename could have had its filename trun…8.8
- CVE-2022-46875The executable file warning was not presented when downloadi…6.5
- CVE-2022-46877By confusing the browser, the fullscreen notification could …4.3
- CVE-2022-46878Mozilla developers Randell Jesup, Valentin Gosu, Olli Pettay…8.8
- CVE-2022-46879Mozilla developers and community members Lukas Bernhard, Gab…8.8
- CVE-2022-46880A missing check related to tex units could have led to a use…6.5
- CVE-2022-46881An optimization in WebGL was incorrect in some cases, and co…8.8
- CVE-2022-46882A use-after-free in WebGL extensions could have led to a pot…9.8
- CVE-2022-46883Mozilla developers Gabriele Svelto, Yulia Startsev, Andrew M…8.8
- CVE-2022-46884A potential use-after-free vulnerability existed in SVG Imag…8.8
- CVE-2022-46885Mozilla developers Timothy Nikkel, Ashley Hale, and the Mozi…8.8
Are you affected by CVE-2022-4688?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST