{"answers":{"affected":"It affects 10 products.","exploited":"There is no known exploitation of CVE-2019-4056 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-4056 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-4056 is a medium-severity vulnerability in Ibm Maximo Asset Management, published on 6 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-4056 and fix it if it is affected.\n\nWhat it is: CVE-2019-4056 is a medium-severity vulnerability in Ibm Maximo Asset Management, published on 6 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-4056 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-2019-4056/ (Markdown: https://insights.sbomify.com/CVE-2019-4056/index.md)","id":"CVE-2019-4056","markdown":"https://insights.sbomify.com/CVE-2019-4056/index.md","name":"CVE-2019-4056","record":{"aliases":["GHSA-pj2h-fwqg-5c5m"],"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":"Attackers can upload malicious files to IBM Maximo Asset Management due to lack of file type validation, potentially leading to code execution.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"control_desk","vendor":"ibm"},{"product":"maximo_asset_management","vendor":"ibm"},{"product":"maximo_for_aviation","vendor":"ibm"},{"product":"maximo_for_life_sciences","vendor":"ibm"},{"product":"maximo_for_nuclear_power","vendor":"ibm"},{"product":"maximo_for_oil_and_gas","vendor":"ibm"},{"product":"maximo_for_transportation","vendor":"ibm"},{"product":"maximo_for_utilities","vendor":"ibm"},{"product":"smartcloud_control_desk","vendor":"ibm"},{"product":"tivoli_integration_composer","vendor":"ibm"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.0/AC:L/I:L/PR:L/AV:N/A:N/C:N/S:U/UI:N/RC:C/RL:O/E:U","version":"3.0"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"IBM Maximo Asset Management 7.6 Work Centers' application does not validate file type upon upload, allowing attackers to upload malicious files. IBM X-Force ID: 156565.","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":"File upload in Maximo Asset Management","id":"CVE-2019-4056","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:maximo_asset_management","products":["ibm:maximo_asset_management","ibm:smartcloud_control_desk"],"type":"file_upload","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Privilege escalation in DB2 for Linux, UNIX and Windows","id":"CVE-2019-4057"},"packages":[],"prev":{"headline":"Denial of service in MQ","id":"CVE-2019-4055"},"products":["Maximo Asset Management"],"published":"2019-06-06","related":[{"cvss_score":6.8,"headline":"Open redirect in Maximo Asset Management","id":"CVE-2020-4409","kev_date_added":null,"published":"2020-09-16"},{"cvss_score":6.5,"headline":"Open redirect in Maximo Asset Management","id":"CVE-2018-2028","kev_date_added":null,"published":"2019-06-06"},{"cvss_score":6.1,"headline":"Cross-site scripting in Maximo Asset Management","id":"CVE-2019-4644","kev_date_added":null,"published":"2020-04-17"},{"cvss_score":5.5,"headline":"Code injection in Maximo Asset Management","id":"CVE-2019-4364","kev_date_added":null,"published":"2019-06-19"},{"cvss_score":5.4,"headline":"Cross-site scripting in Control Desk","id":"CVE-2021-20559","kev_date_added":null,"published":"2021-05-10"},{"cvss_score":5.4,"headline":"Missing authorization in Maximo Asset Management","id":"CVE-2019-4446","kev_date_added":null,"published":"2020-04-17"},{"cvss_score":5.4,"headline":"Cross-site scripting in Maximo Asset Management","id":"CVE-2019-4749","kev_date_added":null,"published":"2020-04-17"}],"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":"Attackers can upload malicious files to IBM Maximo Asset Management due to lack of file type validation, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2019-4056/"}