# CVE-2023-32699: MeterSphere denial of service vulnerability

> Attackers can cause server resource exhaustion and denial of service by submitting excessively long passwords during login.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **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:** 30 May 2023
- **Updated:** 10 Jan 2025
- **Also known as:** GHSA-qffq-8gf8-mhq7

## What is CVE-2023-32699?

CVE-2023-32699 is a medium-severity denial of service vulnerability in metersphere, published on 30 May 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

MeterSphere is an open source continuous testing platform. Version 2.9.1 and prior are vulnerable to denial of service. ​The `checkUserPassword` method is used to check whether the password provided by the user matches the password saved in the database, and the `CodingUtil.md5` method is used to encrypt the original password with MD5 to ensure that the password will not be saved in plain text when it is stored. If a user submits a very long password when logging in, the system will be forced to execute the long password MD5 encryption process, causing the server CPU and memory to be exhausted, thereby causing a denial of service attack on the server. This issue is fixed in version 2.10.0-lts with a maximum password length.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

It affects 1 product.


Products: Metersphere Metersphere.

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

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

## Is CVE-2023-32699 being exploited?

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

## Other vulnerabilities in metersphere

- [CVE-2023-29944](https://insights.sbomify.com/CVE-2023-29944/): Command injection in n/a (critical 9.8)
- [CVE-2021-45790](https://insights.sbomify.com/CVE-2021-45790/): File upload in n/a (critical 9.8)
- [CVE-2021-45788](https://insights.sbomify.com/CVE-2021-45788/): SQL injection in n/a (high 8.8)
- [CVE-2023-25573](https://insights.sbomify.com/CVE-2023-25573/): Improper access control to download file in metersphere (high 8.6)
- [CVE-2022-23512](https://insights.sbomify.com/CVE-2022-23512/): Metersphere is vulnerable to Path Injection. (high 7.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-32699 is a medium-severity denial of service vulnerability in metersphere, published on 30 May 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-32699 exists.

Affected product: metersphere. 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-32699/ (Markdown: https://insights.sbomify.com/CVE-2023-32699/index.md)
```

## Sources

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

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