{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-52723 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2023-52723 is a high-severity vulnerability in n/a, published on 29 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-52723 and fix it if it is affected.\n\nWhat it is: CVE-2023-52723 is a high-severity vulnerability in n/a, published on 29 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-52723 in the wild and no public exploit code.\n\nAffected product: n/a. 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-52723/ (Markdown: https://insights.sbomify.com/CVE-2023-52723/index.md)","id":"CVE-2023-52723","markdown":"https://insights.sbomify.com/CVE-2023-52723/index.md","name":"CVE-2023-52723","record":{"aliases":["DEBIAN-CVE-2023-52723","DLA-3809-1","GHSA-v8mx-hp8h-89vc","UBUNTU-CVE-2023-52723"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"KDE libksieve library","requires_auth":"low_privilege","summary":"An attacker with log access can read cleartext passwords due to a variable assignment error in the KDE libksieve library.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"In KDE libksieve before 23.03.80, kmanagesieve/session.cpp places a cleartext password in server logs because a username variable is accidentally given a password value.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Hardcoded credentials in n/a","id":"CVE-2023-52723","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2023"},"n_packages":0,"n_references":5,"next":{"headline":"Memory corruption in n/a","id":"CVE-2023-52724"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2023-52722"},"products":["n/a"],"published":"2024-04-29","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["n/a"]},"summary":"An attacker with log access can read cleartext passwords due to a variable assignment error in the KDE libksieve library.","url":"https://insights.sbomify.com/CVE-2023-52723/"}