{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-4521 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-4521 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-4521 is a high-severity unsafe deserialization vulnerability in Ibm Maximo Asset Management, published on 15 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-4521 and fix it if it is affected.\n\nWhat it is: CVE-2020-4521 is a high-severity unsafe deserialization vulnerability in Ibm Maximo Asset Management, published on 15 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-4521 in the wild and no public exploit code.\n\nAffected product: Ibm Maximo Asset Management. 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-2020-4521/ (Markdown: https://insights.sbomify.com/CVE-2020-4521/index.md)","id":"CVE-2020-4521","markdown":"https://insights.sbomify.com/CVE-2020-4521/index.md","name":"CVE-2020-4521","record":{"aliases":["GHSA-cggp-hg98-4chw"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Maximo Asset Management","requires_auth":"low_privilege","summary":"Remote authenticated attackers can execute arbitrary code on IBM Maximo Asset Management via unsafe Java deserialization.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"maximo_asset_management","vendor":"ibm"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.0/AC:L/A:H/AV:N/I:H/S:U/C:H/UI:N/PR:L/E:U/RC:C/RL:O","version":"3.0"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"IBM Maximo Asset Management 7.6.0 and 7.6.1 could allow a remote authenticated attacker to execute arbitrary code on the system, caused by an unsafe deserialization in Java. By sending specially-crafted request, an attacker could exploit this vulnerability to execute arbitrary code on the system. IBM X-Force ID: 182396.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Deserialization in Maximo Asset Management","id":"CVE-2020-4521","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:maximo_asset_management","products":["ibm:maximo_asset_management"],"type":"deserialization","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in Engineering Workflow Management","id":"CVE-2020-4522"},"packages":[],"prev":{"headline":"Cross-site scripting in Cognos Analytics","id":"CVE-2020-4520"},"products":["Maximo Asset Management"],"published":"2020-09-15","related":[{"cvss_score":9.8,"headline":"Auth bypass in Maximo Asset Management","id":"CVE-2020-4493","kev_date_added":null,"published":"2020-10-05"},{"cvss_score":9.8,"headline":"SQL injection in Maximo Asset Management","id":"CVE-2017-1175","kev_date_added":null,"published":"2017-07-05"},{"cvss_score":8.8,"headline":"Hardcoded credentials in Maximo Asset Management","id":"CVE-2018-1524","kev_date_added":null,"published":"2018-08-03"},{"cvss_score":8.8,"headline":"SQL injection in Maximo Asset Management","id":"CVE-2018-1414","kev_date_added":null,"published":"2018-02-22"},{"cvss_score":8.8,"headline":"File upload in Maximo Asset Management","id":"CVE-2017-1499","kev_date_added":null,"published":"2018-02-14"},{"cvss_score":8.8,"headline":"Command injection in Maximo Asset Management","id":"CVE-2016-9984","kev_date_added":null,"published":"2017-06-13"}],"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-09-16","vendors":["IBM"]},"summary":"Remote authenticated attackers can execute arbitrary code on IBM Maximo Asset Management via unsafe Java deserialization.","url":"https://insights.sbomify.com/CVE-2020-4521/"}