CVE-2022-4847 json
Incorrectly Specified Destination in a Communication Channel in usememos/memos
published 2022-12-29 3 y ago modified 2026-06-17 4 mo ago also GHSA-r7hg-2cpp-8wqq , GO-2022-1264 , EUVD-2022-7730
- cvss
- 8.3
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 52%
- public exploits
- 0
- none known
Summary
Incorrectly Specified Destination in a Communication Channel in GitHub repository usememos/memos prior to 0.9.1.
Patch / fix
- go github.com/usememos/memos 0.9.1
- usememos usememos/memos 0.9.1
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 19 mo ago
Exploit prediction
0.69% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- huntr.dev https://huntr.dev/bounties/ff6d4b5a-5e75-4a14-b5ce-f318f8613b73 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 8.3 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:H |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/usememos/memos | <0.9.1 |
0.9.1 |
Affected products
- usememos usememos/memos
Classification
- Weakness
-
- CWE-941 Incorrectly Specified Destination in a Communication Channel
References
-
github.com
/usememos/memos/commit/c9bb2b785dc5852655405d5c9ab127a2d5aa3948
web, patch, third-party-advisory
-
huntr.dev
/bounties/ff6d4b5a-5e75-4a14-b5ce-f318f8613b73
web, exploit, patch, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-4847
advisory
-
github.com
/usememos/memos
package
-
github.com
/advisories/GHSA-r7hg-2cpp-8wqq
advisory
Sources
- CVE List CVE-2022-4847
- GitHub Advisory GHSA-r7hg-2cpp-8wqq
- NVD CVE-2022-4847
- OSV GO-2022-1264
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.