{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-4291 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-4291 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-4291 is a medium-severity vulnerability in IBM Maximo Anywhere, published on 16 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-4291 and fix it if it is affected.\n\nWhat it is: CVE-2019-4291 is a medium-severity vulnerability in IBM Maximo Anywhere, published on 16 Feb 2022. 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-2019-4291 in the wild and no public exploit code.\n\nAffected product: IBM Maximo Anywhere. 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-4291/ (Markdown: https://insights.sbomify.com/CVE-2019-4291/index.md)","id":"CVE-2019-4291","markdown":"https://insights.sbomify.com/CVE-2019-4291/index.md","name":"CVE-2019-4291","record":{"aliases":["GHSA-78gp-57mf-h678"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Maximo Anywhere","requires_auth":"none","summary":"Attackers can reverse engineer the application due to missing binary protection, potentially exposing sensitive logic or data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"maximo_anywhere","vendor":"ibm"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.0/S:U/A:N/UI:N/AV:N/C:L/PR:N/AC:L/I:L/RC:C/RL:O/E:U","version":"3.0"},"cwes":[{"id":"CWE-326","name":"Inadequate Encryption Strength"}],"description":"IBM Maximo Anywhere 7.6.4.0 could allow an attacker to reverse engineer the application due to the lack of binary protection precautions. IBM X-Force ID: 160697.","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":"Information disclosure in Maximo Anywhere","id":"CVE-2019-4291","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"File upload in Security Guardium","id":"CVE-2019-4292"},"packages":[],"prev":{"headline":"Information disclosure in Maximo Anywhere","id":"CVE-2019-4288"},"products":["Maximo Anywhere"],"published":"2022-02-16","related":[{"cvss_score":5.4,"headline":"Cross-site scripting in Maximo Anywhere","id":"CVE-2017-1604","kev_date_added":null,"published":"2018-02-21"},{"cvss_score":5,"headline":"Security feature bypass in n/a","id":"CVE-2015-4945","kev_date_added":null,"published":"2015-07-26"},{"cvss_score":4.3,"headline":"Information disclosure in Maximo Anywhere","id":"CVE-2019-4286","kev_date_added":null,"published":"2020-04-29"},{"cvss_score":4.3,"headline":"Information disclosure in Maximo Anywhere","id":"CVE-2019-4288","kev_date_added":null,"published":"2020-04-29"},{"cvss_score":3.5,"headline":"Information disclosure in Maximo Anywhere","id":"CVE-2019-4349","kev_date_added":null,"published":"2020-11-03"},{"cvss_score":2.4,"headline":"Information disclosure in Maximo Anywhere","id":"CVE-2019-4352","kev_date_added":null,"published":"2022-02-16"}],"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 reverse engineer the application due to missing binary protection, potentially exposing sensitive logic or data.","url":"https://insights.sbomify.com/CVE-2019-4291/"}