{"answers":{"affected":"It affects 13 products.","exploited":"There is no known exploitation of CVE-2013-3323 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2013-3323 yet. Limit exposure of the affected software until one is available.","what":"CVE-2013-3323 is a critical vulnerability in Ibm Maximo Asset Management, published on 18 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2013-3323 and fix it if it is affected.\n\nWhat it is: CVE-2013-3323 is a critical vulnerability in Ibm Maximo Asset Management, published on 18 Feb 2020. 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-2013-3323 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-2013-3323/ (Markdown: https://insights.sbomify.com/CVE-2013-3323/index.md)","id":"CVE-2013-3323","markdown":"https://insights.sbomify.com/CVE-2013-3323/index.md","name":"CVE-2013-3323","record":{"aliases":["GHSA-5h7g-4px8-37g8"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["privilege_escalation","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"IBM Maximo Asset Management","requires_auth":"none","summary":"Attackers can gain unauthorized access and escalate privileges in IBM Maximo when WebSeal with Basic Authentication is used due to session invalidation failures.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"change_and_configuration_management_database","vendor":"ibm"},{"product":"maximo_asset_management","vendor":"ibm"},{"product":"maximo_asset_management_essentials","vendor":"ibm"},{"product":"maximo_for_government","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":"maximo_service_desk","vendor":"ibm"},{"product":"smartcloud_control_desk","vendor":"ibm"},{"product":"tivoli_asset_management_for_it","vendor":"ibm"},{"product":"tivoli_service_request_manager","vendor":"ibm"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"A Privilege Escalation Vulnerability exists in IBM Maximo Asset Management 7.5, 7.1, and 6.2, when WebSeal with Basic Authentication is used, due to a failure to invalidate the authentication session, which could let a malicious user obtain unauthorized access.","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":"Privilege escalation in n/a","id":"CVE-2013-3323","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:maximo_asset_management","products":["ibm:maximo_asset_management","ibm:maximo_asset_management_essentials","ibm:smartcloud_control_desk"],"type":"privilege_escalation","year":"2013"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in n/a","id":"CVE-2013-3324"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2013-3322"},"products":["n/a"],"published":"2020-02-18","related":[{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2015-0104","kev_date_added":null,"published":"2017-04-24"},{"cvss_score":6.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2012-0714","kev_date_added":null,"published":"2012-09-10"},{"cvss_score":6.8,"headline":"Auth bypass in n/a","id":"CVE-2012-2183","kev_date_added":null,"published":"2012-09-10"},{"cvss_score":6.8,"headline":"Auth bypass in n/a","id":"CVE-2012-2184","kev_date_added":null,"published":"2012-09-10"},{"cvss_score":6.5,"headline":"Path traversal in n/a","id":"CVE-2015-0107","kev_date_added":null,"published":"2017-04-24"},{"cvss_score":6.5,"headline":"Hardcoded credentials in n/a","id":"CVE-2015-4966","kev_date_added":null,"published":"2015-11-08"}],"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":"Attackers can gain unauthorized access and escalate privileges in IBM Maximo when WebSeal with Basic Authentication is used due to session invalidation failures.","url":"https://insights.sbomify.com/CVE-2013-3323/"}