{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2021-38977 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-38977 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-38977 is a low-severity vulnerability in Ibm Security Key Lifecycle Manager, published on 15 Nov 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-38977 and fix it if it is affected.\n\nWhat it is: CVE-2021-38977 is a low-severity vulnerability in Ibm Security Key Lifecycle Manager, published on 15 Nov 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-38977 in the wild and no public exploit code.\n\nAffected product: Ibm Security Key Lifecycle Manager. 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-2021-38977/ (Markdown: https://insights.sbomify.com/CVE-2021-38977/index.md)","id":"CVE-2021-38977","markdown":"https://insights.sbomify.com/CVE-2021-38977/index.md","name":"CVE-2021-38977","record":{"aliases":["GHSA-vq56-wjh5-mwqf"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Key Lifecycle Manager","requires_auth":"none","summary":"Attackers can steal session cookies via insecure HTTP links, potentially leading to account takeover in IBM Tivoli Key Lifecycle Manager.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"security_guardium_key_lifecycle_manager","vendor":"ibm"},{"product":"security_key_lifecycle_manager","vendor":"ibm"}],"cvss":{"score":3.1,"severity":"low","source":"cna","vector":"CVSS:3.0/AV:N/C:L/UI:R/AC:H/PR:N/S:U/I:N/A:N/RC:C/RL:O/E:U","version":"3.0"},"cwes":[{"id":"CWE-311","name":"Missing Encryption of Sensitive Data"}],"description":"IBM Tivoli Key Lifecycle Manager 3.0, 3.0.1, 4.0, and 4.1 does not set the secure attribute on authorization tokens or session cookies. Attackers may be able to get the cookie values by sending a http:// link to a user or by planting this link in a site the user goes to. The cookie will be sent to the insecure link and the attacker can then obtain the cookie value by snooping the traffic. IBM X-Force ID: 212782.","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 Security Key Lifecycle Manager","id":"CVE-2021-38977","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:security_key_lifecycle_manager","products":["ibm:security_key_lifecycle_manager"],"type":"information_disclosure","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in Security Key Lifecycle Manager","id":"CVE-2021-38978"},"packages":[],"prev":{"headline":"Hardcoded credentials in Security Key Lifecycle Manager","id":"CVE-2021-38976"},"products":["Security Key Lifecycle Manager"],"published":"2021-11-15","related":[{"cvss_score":8.5,"headline":"IBM Security Guardium Key Lifecycle Manager file upload","id":"CVE-2023-25921","kev_date_added":null,"published":"2024-02-29"},{"cvss_score":8.5,"headline":"IBM Security Guardium Key Lifecycle Manager command injection","id":"CVE-2023-25925","kev_date_added":null,"published":"2024-02-28"},{"cvss_score":6.6,"headline":"IBM Security Guardium Key Lifecycle Manager file upload","id":"CVE-2023-47706","kev_date_added":null,"published":"2023-12-20"},{"cvss_score":6.2,"headline":"Hardcoded credentials in Security Key Lifecycle Manager","id":"CVE-2021-38976","kev_date_added":null,"published":"2021-11-15"},{"cvss_score":5.9,"headline":"Information disclosure in Security Key Lifecycle Manager","id":"CVE-2021-38978","kev_date_added":null,"published":"2021-11-15"},{"cvss_score":5.5,"headline":"IBM Security Guardium Key Lifecycle Manager XML external entity injection","id":"CVE-2023-25926","kev_date_added":null,"published":"2024-02-29"},{"cvss_score":5.4,"headline":"IBM Security Guardium Key Lifecycle Manager cross-site scripting","id":"CVE-2023-47707","kev_date_added":null,"published":"2023-12-20"}],"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 steal session cookies via insecure HTTP links, potentially leading to account takeover in IBM Tivoli Key Lifecycle Manager.","url":"https://insights.sbomify.com/CVE-2021-38977/"}