{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-38505 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-38505 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-38505 is a high-severity denial of service vulnerability in ravenclaw900 DietPi-Dashboard, published on 27 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-38505 and fix it if it is affected.\n\nWhat it is: CVE-2023-38505 is a high-severity denial of service vulnerability in ravenclaw900 DietPi-Dashboard, published on 27 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-38505 in the wild and no public exploit code.\n\nAffected product: ravenclaw900 DietPi-Dashboard. 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-38505/ (Markdown: https://insights.sbomify.com/CVE-2023-38505/index.md)","id":"CVE-2023-38505","markdown":"https://insights.sbomify.com/CVE-2023-38505/index.md","name":"CVE-2023-38505","record":{"aliases":["GHSA-3jr4-9rxf-fr44"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"DietPi web dashboard","requires_auth":"none","summary":"An attacker can cause a denial of service by initiating a TLS connection and never completing the handshake, blocking legitimate users from accessing the dashboard.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"dietpi-dashboard","vendor":"dietpi-dashboard_project"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-667","name":"Improper Locking"},{"id":"CWE-412","name":"Unrestricted Externally Accessible Lock"},{"id":"CWE-410","name":"Insufficient Resource Pool"}],"description":"DietPi-Dashboard is a web dashboard for the operating system DietPi. The dashboard only allows for one TLS handshake to be in process at a given moment. Once a TCP connection is established in HTTPS mode, it will assume that it should be waiting for a handshake, and will stay this way indefinitely until a handshake starts or some error occurs. In version 0.6.1, this can be exploited by simply not starting the handshake, preventing any other TLS handshakes from getting through. An attacker can lock the dashboard in a state where it is waiting for a TLS handshake from the attacker, who won't provide it. This prevents any legitimate traffic from getting to the dashboard, and can last indefinitely. Version 0.6.2 has a patch for this issue. As a workaround, do not use HTTPS mode on the open internet where anyone can connect. Instead, put a reverse proxy in front of the dashboard, and have it handle any HTTPS connections.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"DietPi-Dashboard Insufficient TLS Handshake Pool","id":"CVE-2023-38505","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2023"},"n_packages":0,"n_references":4,"next":{"headline":"Cross-site Scripting (XSS) when pasting HTML into the rich text editor in Joplin","id":"CVE-2023-38506"},"packages":[],"prev":{"headline":"Sails DoS vulnerability for apps with sockets enabled","id":"CVE-2023-38504"},"products":["DietPi-Dashboard"],"published":"2023-07-27","related":[],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-10-10","vendors":["ravenclaw900"]},"summary":"An attacker can cause a denial of service by initiating a TLS connection and never completing the handshake, blocking legitimate users from accessing the dashboard.","url":"https://insights.sbomify.com/CVE-2023-38505/"}