CVE-2022-32169 json
bytebase - Improper Authorization
published 2022-09-28 4 y ago modified 2026-06-17 4 mo ago also GHSA-5rc4-v5mj-g8c4 , EUVD-2022-6712
- 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 issues“ for which an unauthorized user can view the “OPEN” and “CLOSED” issues by “Admin” and the affected endpoint is “/issue”.
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 17 mo ago
Exploit prediction
0.66% chance of exploitation in the next 30 days, higher than 51% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- mend.io https://www.mend.io/vulnerability-database/CVE-2022-32169 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
References
-
mend.io
/vulnerability-database/CVE-2022-32169
web, exploit, third-party-advisory
- github.com /bytebase/bytebase/blob/1.0.4/frontend/src/store/modules/issue.ts#L108-L187
-
nvd.nist.gov
/vuln/detail/CVE-2022-32169
advisory
-
github.com
/bytebase/bytebase
package
-
github.com
/bytebase/bytebase/blob/1.0.4/frontend/src/store/modules/issue.ts#L108-#L187
web
Sources
- CVE List CVE-2022-32169
- GitHub Advisory GHSA-5rc4-v5mj-g8c4
- NVD CVE-2022-32169
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.