{"answers":{"affected":"It affects 6 products.","exploited":"There is no known exploitation of CVE-2011-4817 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2011-4817 yet. Limit exposure of the affected software until one is available.","what":"CVE-2011-4817 is a medium-severity vulnerability in Ibm Maximo Asset Management, published on 13 Mar 2012. 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-2011-4817 and fix it if it is affected.\n\nWhat it is: CVE-2011-4817 is a medium-severity vulnerability in Ibm Maximo Asset Management, published on 13 Mar 2012. 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-2011-4817 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-2011-4817/ (Markdown: https://insights.sbomify.com/CVE-2011-4817/index.md)","id":"CVE-2011-4817","markdown":"https://insights.sbomify.com/CVE-2011-4817/index.md","name":"CVE-2011-4817","record":{"aliases":["GHSA-3j4r-3gwf-p2pm"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Maximo Asset Management","requires_auth":"low_privilege","summary":"Authenticated users can view usernames via the Help menu, potentially aiding targeted attacks against specific accounts.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"maximo_asset_management","vendor":"ibm"},{"product":"maximo_asset_management_essentials","vendor":"ibm"},{"product":"maximo_service_desk","vendor":"ibm"},{"product":"tivoli_asset_management_for_it","vendor":"ibm"},{"product":"tivoli_change_and_configuration_management_database","vendor":"ibm"},{"product":"trivoli_service_request_manager","vendor":"ibm"}],"cvss":{"score":4,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:S/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"The About option on the Help menu in IBM Maximo Asset Management and Asset Management Essentials 6.2, 7.1, and 7.5; IBM Tivoli Asset Management for IT 6.2, 7.1, and 7.2; IBM Tivoli Service Request Manager 7.1 and 7.2; IBM Maximo Service Desk 6.2; and IBM Tivoli Change and Configuration Management Database (CCMDB) 6.2, 7.1, and 7.2 shows the username, which might allow remote authenticated users to have an unspecified impact via a targeted attack against the corresponding user account.","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 n/a","id":"CVE-2011-4817","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:maximo_asset_management","products":["ibm:maximo_asset_management","ibm:maximo_asset_management_essentials"],"type":"information_disclosure","year":"2011"},"n_packages":0,"n_references":6,"next":{"headline":"Open redirect in n/a","id":"CVE-2011-4818"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2011-4816"},"products":["n/a"],"published":"2012-03-13","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-07","vendors":["n/a"]},"summary":"Authenticated users can view usernames via the Help menu, potentially aiding targeted attacks against specific accounts.","url":"https://insights.sbomify.com/CVE-2011-4817/"}