{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-49933 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2023-49933 is a high-severity vulnerability in n/a, published on 14 Dec 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-49933 and fix it if it is affected.\n\nWhat it is: CVE-2023-49933 is a high-severity vulnerability in n/a, published on 14 Dec 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-49933 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-49933/ (Markdown: https://insights.sbomify.com/CVE-2023-49933/index.md)","id":"CVE-2023-49933","markdown":"https://insights.sbomify.com/CVE-2023-49933/index.md","name":"CVE-2023-49933","record":{"aliases":["DEBIAN-CVE-2023-49933","GHSA-hgjx-j8hg-pxrf","UBUNTU-CVE-2023-49933"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Slurm workload manager","requires_auth":"none","summary":"Attackers can bypass message integrity checks in Slurm RPC traffic, allowing modification of transmitted data.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"slurm","vendor":"schedmd"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-924","name":"Improper Enforcement of Message Integrity During Transmission in a Communication Channel"}],"description":"An issue was discovered in SchedMD Slurm 22.05.x, 23.02.x, and 23.11.x. There is Improper Enforcement of Message Integrity During Transmission in a Communication Channel. This allows attackers to modify RPC traffic in a way that bypasses message hash checks. The fixed versions are 22.05.11, 23.02.7, and 23.11.1.","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":"Security feature bypass in n/a","id":"CVE-2023-49933","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2023"},"n_packages":0,"n_references":4,"next":{"headline":"SQL injection in n/a","id":"CVE-2023-49934"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2023-49932"},"products":["n/a"],"published":"2023-12-14","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2023-49934","kev_date_added":null,"published":"2023-12-14"},{"cvss_score":9.8,"headline":"Use after free in n/a","id":"CVE-2023-49937","kev_date_added":null,"published":"2023-12-14"},{"cvss_score":8.8,"headline":"Auth bypass in n/a","id":"CVE-2023-49935","kev_date_added":null,"published":"2023-12-14"},{"cvss_score":8.2,"headline":"Privilege escalation in n/a","id":"CVE-2023-49938","kev_date_added":null,"published":"2023-12-14"},{"cvss_score":8.1,"headline":"Path traversal in n/a","id":"CVE-2016-10030","kev_date_added":null,"published":"2017-01-05"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2017-15566","kev_date_added":null,"published":"2017-11-01"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2025-11-04","vendors":["n/a"]},"summary":"Attackers can bypass message integrity checks in Slurm RPC traffic, allowing modification of transmitted data.","url":"https://insights.sbomify.com/CVE-2023-49933/"}