# CVE-2024-10620: knightliao Disconf Configuration Center list improper authentication

> Remote attackers can bypass authentication in the Disconf Configuration Center to access configuration lists without proper credentials.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Nov 2024
- **Updated:** 1 Nov 2024
- **Also known as:** GHSA-rrqf-vmwv-g72p

## What is CVE-2024-10620?

CVE-2024-10620 is a medium-severity authentication bypass vulnerability in knightliao Disconf, published on 1 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in knightliao Disconf 2.6.36. It has been classified as critical. This affects an unknown part of the file /api/config/list of the component Configuration Center. The manipulation leads to improper authentication. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2024-10620?


## How do I fix CVE-2024-10620?

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

## Is CVE-2024-10620 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-10620 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-10620 and fix it if it is affected.

What it is: CVE-2024-10620 is a medium-severity authentication bypass vulnerability in knightliao Disconf, published on 1 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-10620 exists.

Affected product: knightliao Disconf. 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-2024-10620/ (Markdown: https://insights.sbomify.com/CVE-2024-10620/index.md)
```

## Sources

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

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