{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-0779 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-0779 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-0779 is a critical unsafe deserialization vulnerability in n/a, published on 11 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-0779 and fix it if it is affected.\n\nWhat it is: CVE-2016-0779 is a critical unsafe deserialization vulnerability in n/a, published on 11 Apr 2017. 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-2016-0779 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-2016-0779/ (Markdown: https://insights.sbomify.com/CVE-2016-0779/index.md)","id":"CVE-2016-0779","markdown":"https://insights.sbomify.com/CVE-2016-0779/index.md","name":"CVE-2016-0779","record":{"aliases":["CVE-2015-8581","GHSA-g7jw-7782-jjv9"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Java EE application server","requires_auth":"none","summary":"Remote attackers can execute arbitrary code via crafted serialized objects in Apache TomEE, requiring an upgrade to secure the application server.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"tomee","vendor":"apache"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"The EjbObjectInputStream class in Apache TomEE before 1.7.4 and 7.x before 7.0.0-M3 allows remote attackers to execute arbitrary code via a crafted serialized object.","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":"Deserialization in n/a","id":"CVE-2016-0779","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2016"},"n_packages":0,"n_references":6,"next":{"headline":"Denial of service in Cloud Foundry","id":"CVE-2016-0780"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2016-0778"},"products":["n/a"],"published":"2017-04-11","related":[{"cvss_score":9.8,"headline":"Remote code execution in Apache TomEE","id":"CVE-2020-13931","kev_date_added":null,"published":"2020-12-17"},{"cvss_score":9.8,"headline":"Missing Authentication for Critical Function in Apache TomEE","id":"CVE-2020-11969","kev_date_added":null,"published":"2020-06-15"},{"cvss_score":9.8,"headline":"XML external entity injection in Terracotta Quartz Scheduler","id":"CVE-2019-13990","kev_date_added":null,"published":"2019-07-26"},{"cvss_score":7.5,"headline":"Out-of-Memory Error in Bouncy Castle Crypto","id":"CVE-2019-17359","kev_date_added":null,"published":"2019-10-08"},{"cvss_score":6.1,"headline":"Apache TomEE console vulnerable to Cross-site Scripting","id":"CVE-2018-8031","kev_date_added":null,"published":"2018-07-23"}],"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":"2024-08-05","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary code via crafted serialized objects in Apache TomEE, requiring an upgrade to secure the application server.","url":"https://insights.sbomify.com/CVE-2016-0779/"}