CVE-2023-1164 json
KylinSoft kylin-activation File Import improper authorization
published 2023-03-03 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-23446
- cvss
- 8.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 32%
- public exploits
- 0
- none known
Summary
A vulnerability was found in KylinSoft kylin-activation on KylinOS and classified as critical. Affected by this issue is some unknown functionality of the component File Import. The manipulation leads to improper authorization. The attack needs to be approached locally. The exploit has been disclosed to the public and may be used. Upgrading to version 1.3.11-23 and 1.30.10-5.p23 is able to address this issue. It is recommended to upgrade the affected component. The identifier of this vulnerability is VDB-222260.
Patch / fix
- kylinos kylin_os 1.3.11-23, 1.30.10-5.p23
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2 y ago
Exploit prediction
0.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/i900008/vulndb/blob/main/kylin-activation_vuln.md referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.4 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.0 | 8.4 | CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- KylinSoft kylin-activation
Classification
References
-
github.com
/i900008/vulndb/blob/main/kylin-activation_vuln.md
broken-link, exploit, third-party-advisory
-
vuldb.com
/?id.222260
vdb-entry, technical-description, third-party-advisory
-
vuldb.com
/?ctiid.222260
signature, permissions-required, third-party-advisory, vdb-entry
Sources
- CVE List CVE-2023-1164
- NVD CVE-2023-1164
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.