{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-34050 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-34050 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-34050 is a medium-severity unsafe deserialization vulnerability in Spring AMQP, published on 19 Oct 2023. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-34050 and fix it if it is affected.\n\nWhat it is: CVE-2023-34050 is a medium-severity unsafe deserialization vulnerability in Spring AMQP, published on 19 Oct 2023. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-34050 in the wild and no public exploit code.\n\nAffected product: Spring AMQP. 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-34050/ (Markdown: https://insights.sbomify.com/CVE-2023-34050/index.md)","id":"CVE-2023-34050","markdown":"https://insights.sbomify.com/CVE-2023-34050/index.md","name":"CVE-2023-34050","record":{"aliases":["GHSA-24f5-5fmf-pwmc"],"analysis":{"component_type":"library","fix_type":"configuration_change","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Spring AMQP library","requires_auth":"high_privilege","summary":"Attackers can execute arbitrary code if untrusted users can send messages to a RabbitMQ broker using Spring AMQP without configured deserialization allowlists.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"vmware","cpe":[{"product":"spring_advanced_message_queuing_protocol","vendor":"vmware"}],"cvss":{"score":5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"In spring AMQP versions 1.0.0 to\n2.4.16 and 3.0.0 to 3.0.9 , allowed list patterns for deserializable class\nnames were added to Spring AMQP, allowing users to lock down deserialization of\ndata in messages from untrusted sources; however by default, when no allowed\nlist was provided, all classes could be deserialized.\n\nSpecifically, an application is\nvulnerable if\n\n   *  the\n     SimpleMessageConverter or SerializerMessageConverter is used\n\n   *  the user\n     does not configure allowed list patterns\n\n   *  untrusted\n     message originators gain permissions to write messages to the RabbitMQ\n     broker to send malicious content","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2023-10-20","github_poc":1,"max_poc_stars":13,"metasploit":0,"nuclei":0,"refs":[{"date":"2023-10-20T05:46:15Z","kind":"github_poc","ref":"https://github.com/X1r0z/spring-amqp-deserialization","stars":13,"title":"PoC of Spring AMQP Deserialization Vulnerability (CVE-2023-34050)"}],"tier":"poc_unverified"},"has_fix":false,"headline":"Spring AMQP Deserialization Vulnerability","id":"CVE-2023-34050","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in VMware Aria Operations for Logs","id":"CVE-2023-34051"},"packages":[],"prev":{"headline":"Salt security advisory release - 2023-OCT-27","id":"CVE-2023-34049"},"products":["Spring AMQP"],"published":"2023-10-19","related":[{"cvss_score":6.8,"headline":"Log4j2 AmqpAppender disables TLS hostname verification by default","id":"CVE-2026-59272","kev_date_added":null,"published":"2026-08-27"},{"cvss_score":6.6,"headline":"Deserialization in Spring AMQP","id":"CVE-2026-59275","kev_date_added":null,"published":"2026-08-27"},{"cvss_score":6.5,"headline":"In Spring AMQP the link credit never replenished on listener exception path","id":"CVE-2026-59320","kev_date_added":null,"published":"2026-08-27"},{"cvss_score":6.5,"headline":"Unbounded decompression of attacker-supplied compressed message bodies","id":"CVE-2026-47860","kev_date_added":null,"published":"2026-08-26"},{"cvss_score":6.5,"headline":"Deserialization of Untrusted Data in Spring AMQP","id":"CVE-2021-22095","kev_date_added":null,"published":"2021-11-30"},{"cvss_score":6.5,"headline":"Deserialization of Untrusted Data in Spring AMQP","id":"CVE-2021-22097","kev_date_added":null,"published":"2021-10-28"},{"cvss_score":5.3,"headline":"Admin password disclosed in BrokerNotAliveException message","id":"CVE-2026-59271","kev_date_added":null,"published":"2026-08-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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-12","vendors":["Spring"]},"summary":"Attackers can execute arbitrary code if untrusted users can send messages to a RabbitMQ broker using Spring AMQP without configured deserialization allowlists.","url":"https://insights.sbomify.com/CVE-2023-34050/"}