{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2014-0893 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2014-0893 yet. Limit exposure of the affected software until one is available.","what":"CVE-2014-0893 is a medium-severity cross-site scripting vulnerability in Ibm Maximo Asset Management, published on 26 May 2014. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2014-0893 and fix it if it is affected.\n\nWhat it is: CVE-2014-0893 is a medium-severity cross-site scripting vulnerability in Ibm Maximo Asset Management, published on 26 May 2014. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2014-0893 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-2014-0893/ (Markdown: https://insights.sbomify.com/CVE-2014-0893/index.md)","id":"CVE-2014-0893","markdown":"https://insights.sbomify.com/CVE-2014-0893/index.md","name":"CVE-2014-0893","record":{"aliases":["GHSA-29mp-2hx5-9mm4"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Maximo Asset Management","requires_auth":"low_privilege","summary":"Authenticated attackers can inject malicious scripts into IBM Maximo Asset Management via customreport.jsp, potentially stealing user data or hijacking sessions.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"maximo_asset_management","vendor":"ibm"},{"product":"smartcloud_control_desk","vendor":"ibm"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"AV:N/AC:M/Au:N/C:N/I:P/A:N","version":"2.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Cross-site scripting (XSS) vulnerability in customreport.jsp in IBM Maximo Asset Management 7.5.x before 7.5.0.5 IFIX006 and SmartCloud Control Desk 7.x before 7.5.0.3 and 7.5.1.x before 7.5.1.2 allows remote authenticated users to inject arbitrary web script or HTML via unspecified parameters.","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":"Cross-site scripting in n/a","id":"CVE-2014-0893","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:maximo_asset_management","products":["ibm:maximo_asset_management","ibm:smartcloud_control_desk"],"type":"xss","year":"2014"},"n_packages":0,"n_references":3,"next":{"headline":"Information disclosure in n/a","id":"CVE-2014-0894"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2014-0892"},"products":["n/a"],"published":"2014-05-26","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":"Deserialization in Maximo Asset Management","id":"CVE-2020-4521","kev_date_added":null,"published":"2020-09-15"},{"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-08-06","vendors":["n/a"]},"summary":"Authenticated attackers can inject malicious scripts into IBM Maximo Asset Management via customreport.jsp, potentially stealing user data or hijacking sessions.","url":"https://insights.sbomify.com/CVE-2014-0893/"}