{"answers":{"affected":"2 open source packages ship an affected version, including meshcentral. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-51838 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-51838 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-51838 is a high-severity vulnerability in n/a, published on 2 Feb 2024. 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-51838 and fix it if it is affected.\n\nWhat it is: CVE-2023-51838 is a high-severity vulnerability in n/a, published on 2 Feb 2024. 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-51838 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- meshcentral (npm): affected all versions up to 1.1.16; no fix listed\n- meshcentral (npm): affected all versions up to 1.1.16; no fix listed\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-51838/ (Markdown: https://insights.sbomify.com/CVE-2023-51838/index.md)","id":"CVE-2023-51838","markdown":"https://insights.sbomify.com/CVE-2023-51838/index.md","name":"CVE-2023-51838","record":{"aliases":["GHSA-v269-rrr6-cx6r"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"MeshCentral remote management","requires_auth":"none","summary":"Attackers can exploit broken cryptographic algorithms in MeshCentral to bypass security controls, requiring an upgrade to a secure version.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"meshcentral","vendor":"meshcentral"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"description":"Ylianst MeshCentral 1.1.16 suffers from Use of a Broken or Risky Cryptographic Algorithm.","ecosystems":["npm"],"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":"Ylianst MeshCentral 1.1.16 suffers from Use of a Broken or Risky Cryptographic Algorithm.","id":"CVE-2023-51838","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"weak_cryptography","year":"2023"},"n_packages":2,"n_references":3,"next":{"headline":"DeviceFarmer stf uses DES-ECB","id":"CVE-2023-51839"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.1.16"],"package":"meshcentral","purl":null,"source":"GHSA-v269-rrr6-cx6r"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.1.16"],"package":"meshcentral","purl":"pkg:npm/meshcentral","source":"GHSA-v269-rrr6-cx6r"}],"prev":{"headline":"Ylianst MeshCentral Missing SSL Certificate Validation","id":"CVE-2023-51837"},"products":["n/a"],"published":"2024-02-02","related":[{"cvss_score":9.8,"headline":"Ylianst MeshCentral Missing SSL Certificate Validation","id":"CVE-2023-51837","kev_date_added":null,"published":"2024-01-30"},{"cvss_score":8.4,"headline":"MeshCentral cross-site websocket hijacking (CSWSH) vulnerability","id":"CVE-2024-26135","kev_date_added":null,"published":"2024-02-20"},{"cvss_score":7.5,"headline":"MeshCentral algorithm-downgrade issue","id":"CVE-2023-51842","kev_date_added":null,"published":"2024-01-29"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-16","vendors":["n/a"]},"summary":"Attackers can exploit broken cryptographic algorithms in MeshCentral to bypass security controls, requiring an upgrade to a secure version.","url":"https://insights.sbomify.com/CVE-2023-51838/"}