CVE-2023-4984 json
didi KnowSearch 1 credentials storage
published 2023-09-15 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-54814
- 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
A vulnerability was found in didi KnowSearch 0.3.2/0.3.1.2. It has been rated as problematic. This issue affects some unknown processing of the file /api/es/admin/v3/security/user/1. The manipulation leads to unprotected storage of credentials. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-239795.
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
- github.com https://github.com/didi/KnowSearch/files/12135597/ad1aa7b3-ecee-44b0-a22a-80917ca0fe71.pdf4398935202801712312.pdf referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/didi/KnowSearch/issues/86 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 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.0 | 4.3 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| CNA | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected products
- didi KnowSearch
Classification
- Weakness
-
- CWE-256 Plaintext Storage of a Password
References
-
github.com
/didi/KnowSearch/files/12135597/ad1aa7b3-ecee-44b0-a22a-80917ca0fe71.pdf4398935202801712312.pdf
exploit
-
github.com
/didi/KnowSearch/issues/86
issue-tracking, exploit
-
vuldb.com
/?id.239795
vdb-entry, technical-description, third-party-advisory
-
vuldb.com
/?ctiid.239795
signature, permissions-required, third-party-advisory
Sources
- CVE List CVE-2023-4984
- NVD CVE-2023-4984
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.