# CVE-2023-4984: didi KnowSearch 1 credentials storage

> Remote attackers can access unprotected stored credentials via a specific API endpoint in the KnowSearch application.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-hfpv-wwcx-9hg3

## What is CVE-2023-4984?

CVE-2023-4984 is a medium-severity vulnerability in didi KnowSearch, published on 15 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-256 (Plaintext Storage of a Password)

## Which versions are affected by CVE-2023-4984?

It affects 1 product.


Products: Didiglobal Knowsearch.

## How do I fix CVE-2023-4984?

No fix has been published for CVE-2023-4984 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-4984 being exploited?

There is no known exploitation of CVE-2023-4984 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-4984 and fix it if it is affected.

What it is: CVE-2023-4984 is a medium-severity vulnerability in didi KnowSearch, published on 15 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-4984 in the wild and no public exploit code.

Affected product: didi KnowSearch. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-4984/ (Markdown: https://insights.sbomify.com/CVE-2023-4984/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-4984
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-4984
- OSV: https://osv.dev/vulnerability/CVE-2023-4984

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-4984/
Summaries are generated and may contain mistakes; the official description above is the record.