{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-32699 exists.","fix":"No fix has been published for CVE-2023-32699 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2023-32699 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-32699 exists.\n\nAffected product: metersphere. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-32699/ (Markdown: https://insights.sbomify.com/CVE-2023-32699/index.md)","id":"CVE-2023-32699","markdown":"https://insights.sbomify.com/CVE-2023-32699/index.md","name":"CVE-2023-32699","record":{"aliases":["GHSA-qffq-8gf8-mhq7"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"MeterSphere testing platform","requires_auth":"low_privilege","summary":"Attackers can cause server resource exhaustion and denial of service by submitting excessively long passwords during login.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"metersphere","vendor":"metersphere"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"MeterSphere denial of service vulnerability","id":"CVE-2023-32699","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Command injection in n/a","id":"CVE-2023-32700"},"packages":[],"prev":{"headline":"nfpm vulnerable to Incorrect Default Permissions","id":"CVE-2023-32698"},"products":["metersphere"],"published":"2023-05-30","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2023-29944","kev_date_added":null,"published":"2023-05-08"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2021-45790","kev_date_added":null,"published":"2021-12-27"},{"cvss_score":8.8,"headline":"SQL injection in n/a","id":"CVE-2021-45788","kev_date_added":null,"published":"2021-12-27"},{"cvss_score":8.6,"headline":"Improper access control to download file in metersphere","id":"CVE-2023-25573","kev_date_added":null,"published":"2023-03-09"},{"cvss_score":7.7,"headline":"Metersphere is vulnerable to Path Injection.","id":"CVE-2022-23512","kev_date_added":null,"published":"2022-12-14"},{"cvss_score":7.4,"headline":"Path Traversal In MeterSpere allows file upload to any path","id":"CVE-2022-46178","kev_date_added":null,"published":"2022-12-29"},{"cvss_score":7.2,"headline":"Server-Side Request Forgery in Metersphere leads to Cross-Site Scripting","id":"CVE-2022-23544","kev_date_added":null,"published":"2022-12-27"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-01-10","vendors":["metersphere"]},"summary":"Attackers can cause server resource exhaustion and denial of service by submitting excessively long passwords during login.","url":"https://insights.sbomify.com/CVE-2023-32699/"}