{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-41763 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-41763 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-41763 is a medium-severity vulnerability in IBM Engineering Lifecycle Optimization Publishing, published on 4 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-41763 and fix it if it is affected.\n\nWhat it is: CVE-2024-41763 is a medium-severity vulnerability in IBM Engineering Lifecycle Optimization Publishing, published on 4 Jan 2025. 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-2024-41763 in the wild and no public exploit code.\n\nAffected product: IBM Engineering Lifecycle Optimization Publishing. 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-2024-41763/ (Markdown: https://insights.sbomify.com/CVE-2024-41763/index.md)","id":"CVE-2024-41763","markdown":"https://insights.sbomify.com/CVE-2024-41763/index.md","name":"CVE-2024-41763","record":{"aliases":["GHSA-g5cm-fp5c-4jfp"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Engineering Lifecycle","requires_auth":"none","summary":"Weak cryptographic algorithms in IBM Engineering Lifecycle Optimization Publishing allow attackers to decrypt highly sensitive information.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"engineering_lifecycle_optimization_publishing","vendor":"ibm"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"description":"IBM Engineering Lifecycle Optimization - Publishing 7.0.2 and 7.0.3  uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.","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":"IBM Engineering Lifecycle Optimization - Publishing information disclosure","id":"CVE-2024-41763","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"IBM Engineering Lifecycle Optimization - Publishing directory traversal","id":"CVE-2024-41765"},"packages":[],"prev":{"headline":"IBM Db2 denial of service","id":"CVE-2024-41762"},"products":["Engineering Lifecycle Optimization Publishing"],"published":"2025-01-04","related":[{"cvss_score":7.5,"headline":"IBM Engineering Lifecycle Optimization - Publishing denial of service","id":"CVE-2024-41766","kev_date_added":null,"published":"2025-01-04"},{"cvss_score":7.3,"headline":"IBM Engineering Lifecycle Optimization - Publishing SQL injection","id":"CVE-2024-41767","kev_date_added":null,"published":"2025-01-04"},{"cvss_score":6.5,"headline":"IBM Engineering Lifecycle Optimization - Publishing directory traversal","id":"CVE-2024-41765","kev_date_added":null,"published":"2025-01-04"},{"cvss_score":6.5,"headline":"IBM Engineering Lifecycle Optimization - Publishing unhandled SLL exception","id":"CVE-2024-41768","kev_date_added":null,"published":"2025-01-04"},{"cvss_score":6.5,"headline":"IBM Engineering Lifecycle Optimization Publishing file upload","id":"CVE-2023-45188","kev_date_added":null,"published":"2024-06-09"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-01-06","vendors":["IBM"]},"summary":"Weak cryptographic algorithms in IBM Engineering Lifecycle Optimization Publishing allow attackers to decrypt highly sensitive information.","url":"https://insights.sbomify.com/CVE-2024-41763/"}