{"answers":{"affected":"2 open source packages ship an affected version, including org.apache.qpid:qpid-jms-client. It affects 2 products.","exploited":"There is no known exploitation of CVE-2016-4974 in the wild and no public exploit code.","fix":"Upgrade org.apache.qpid:qpid-jms-client to 0.10.0 or later.","what":"CVE-2016-4974 is a high-severity unsafe deserialization vulnerability in n/a, published on 13 Jul 2016. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-4974 and fix it if it is affected.\n\nWhat it is: CVE-2016-4974 is a high-severity unsafe deserialization vulnerability in n/a, published on 13 Jul 2016. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2016-4974 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.qpid:qpid-jms-client (Maven): affected all versions; fixed in 0.10.0\n- org.apache.qpid:qpid-jms-client (Maven): affected all versions; fixed in 0.10.0\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-2016-4974/ (Markdown: https://insights.sbomify.com/CVE-2016-4974/index.md)","id":"CVE-2016-4974","markdown":"https://insights.sbomify.com/CVE-2016-4974/index.md","name":"CVE-2016-4974","record":{"aliases":["GHSA-f38p-mq64-h784","UBUNTU-CVE-2016-4974"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache Qpid JMS client","requires_auth":"low_privilege","summary":"Remote authenticated users can execute arbitrary code via crafted serialized objects in JMS messages due to unrestricted classpath deserialization.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"amqp_0-x_jms_client","vendor":"apache"},{"product":"jms_client_amqp","vendor":"apache"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Apache Qpid AMQP 0-x JMS client before 6.0.4 and JMS (AMQP 1.0) before 0.10.0 does not restrict the use of classes available on the classpath, which might allow remote authenticated users with permission to send messages to deserialize arbitrary objects and execute arbitrary code by leveraging a crafted serialized object in a JMS ObjectMessage that is handled by the getObject function.","ecosystems":["Maven"],"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":"Improper Input Validation in Apache Qpid AMQP 0-x JMS","id":"CVE-2016-4974","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"deserialization","year":"2016"},"n_packages":2,"n_references":7,"next":{"headline":"mod_userdir CRLF injection","id":"CVE-2016-4975"},"packages":[{"ecosystem":"Maven","fixed":["0.10.0"],"introduced":["0"],"last_affected":[],"package":"org.apache.qpid:qpid-jms-client","purl":null,"source":"GHSA-f38p-mq64-h784"},{"ecosystem":"Maven","fixed":["0.10.0"],"introduced":["0"],"last_affected":[],"package":"org.apache.qpid:qpid-jms-client","purl":"pkg:maven/org.apache.qpid/qpid-jms-client","source":"GHSA-f38p-mq64-h784"}],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2016-4973"},"products":["n/a"],"published":"2016-07-13","related":[],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Remote authenticated users can execute arbitrary code via crafted serialized objects in JMS messages due to unrestricted classpath deserialization.","url":"https://insights.sbomify.com/CVE-2016-4974/"}