CVE-2022-32170 json
bytebase - Improper Authorization
published 4y ago modified 4mo ago also GHSA-9mmc-27gw-w6mq , EUVD-2022-6762
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 51%
- public exploits
- 0
- none known
Summary
The “Bytebase” application does not restrict low privilege user to access admin “projects“ for which an unauthorized user can view the “projects“ created by “Admin” and the affected endpoint is “/api/project?user=${userId}”.
Is CVE-2022-32170 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.66% chance of exploitation in the next 30 days, higher than 51% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- mend.io https://www.mend.io/vulnerability-database/CVE-2022-32170 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 |
| 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/bytebase/bytebase | >=0.1.0, <=1.0.4 |
no fix listed |
Affected products
- bytebase bytebase
Classification
- Weakness
-
- CWE-285 Improper Authorization
References
-
mend.io
/vulnerability-database/CVE-2022-32170
web, exploit, third-party-advisory
-
github.com
/bytebase/bytebase/blob/1.0.4/frontend/src/store/modules/project.ts#L166-L197
web
-
nvd.nist.gov
/vuln/detail/CVE-2022-32170
advisory
-
github.com
/bytebase/bytebase
package
Sources
- CVE List CVE-2022-32170
- GitHub Advisory GHSA-9mmc-27gw-w6mq
- NVD CVE-2022-32170
Fencer Intel 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.