CVE-2022-46959 json
Path Traversal in github.com/go-sonic/sonic
published 2023-01-23 3 y ago modified 2026-06-17 4 mo ago also GHSA-2x48-p6cq-5xcw , GO-2023-1509 , EUVD-2023-0310
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 56%
- public exploits
- 0
- none known
Summary
An issue in the component /admin/backups/work-dir of Sonic v1.0.4 allows attackers to execute a directory traversal.
Patch / fix
- go github.com/go-sonic/sonic 1.0.5
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 19 mo ago
Exploit prediction
0.78% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/go-sonic/sonic/issues/56 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| NVD | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| GitHub | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/go-sonic/sonic | <1.0.5 |
1.0.5 |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
github.com
/go-sonic/sonic/issues/56
web, exploit, issue-tracking, patch, third-party-advisory, report
-
github.com
/go-sonic/sonic/pull/61/commits/3b00266a13fa69284f4b3f4b37d29be8f8e02f31
web, patch
-
nvd.nist.gov
/vuln/detail/CVE-2022-46959
advisory
-
github.com
/go-sonic/sonic
package
-
github.com
/go-sonic/sonic/releases/tag/v1.0.5
web
-
github.com
/advisories/GHSA-2x48-p6cq-5xcw
advisory
Sources
- CVE List CVE-2022-46959
- GitHub Advisory GHSA-2x48-p6cq-5xcw
- NVD CVE-2022-46959
- OSV GO-2023-1509
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.