{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-39020 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-39020 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-39020 is a low-severity vulnerability in IBM Guardium Data Encryption, published on 5 May 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-39020 and fix it if it is affected.\n\nWhat it is: CVE-2021-39020 is a low-severity vulnerability in IBM Guardium Data Encryption, published on 5 May 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-39020 in the wild and no public exploit code.\n\nAffected product: IBM Guardium Data Encryption. 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-39020/ (Markdown: https://insights.sbomify.com/CVE-2021-39020/index.md)","id":"CVE-2021-39020","markdown":"https://insights.sbomify.com/CVE-2021-39020/index.md","name":"CVE-2021-39020","record":{"aliases":["GHSA-cx5r-3fr2-xpjf"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Guardium Data Encryption","requires_auth":"high_privilege","summary":"Attackers can access sensitive data stored in URL parameters via logs or history, requiring an upgrade to IBM Guardium Data Encryption.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"guardium_data_encryption","vendor":"ibm"}],"cvss":{"score":2,"severity":"low","source":"cna","vector":"CVSS:3.0/C:L/PR:H/UI:R/AV:N/S:U/A:N/AC:H/I:N/RC:C/RL:O/E:U","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"IBM Guardium Data Encryption (GDE) 4.0.0.7 and lower stores sensitive information in URL parameters. This may lead to information disclosure if unauthorized parties have access to the URLs via server logs, referrer header or browser history. IBM X-Force ID: 213855.","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 Guardium Data Encryption","id":"CVE-2021-39020","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in Security Guardium Data Encryption","id":"CVE-2021-39021"},"packages":[],"prev":{"headline":"Information disclosure in Engineering Lifecycle Optimization Publishing","id":"CVE-2021-39019"},"products":["Guardium Data Encryption"],"published":"2022-05-05","related":[{"cvss_score":8.8,"headline":"Command injection in Security Guardium Data Encryption","id":"CVE-2019-4713","kev_date_added":null,"published":"2020-08-26"},{"cvss_score":7.4,"headline":"Weak cryptography in Security Guardium Data Encryption","id":"CVE-2019-4698","kev_date_added":null,"published":"2020-08-26"},{"cvss_score":6.8,"headline":"Hardcoded credentials in Security Guardium Data Encryption","id":"CVE-2019-4694","kev_date_added":null,"published":"2020-08-26"},{"cvss_score":6.5,"headline":"Missing authorization in Guardium Data Encryption","id":"CVE-2021-20474","kev_date_added":null,"published":"2021-07-07"},{"cvss_score":6.3,"headline":"Auth bypass in Guardium Data Encryption","id":"CVE-2021-20378","kev_date_added":null,"published":"2021-07-07"},{"cvss_score":6.2,"headline":"Other in Security Guardium Data Encryption","id":"CVE-2021-39022","kev_date_added":null,"published":"2022-03-10"},{"cvss_score":6,"headline":"Hardcoded credentials in Security Guardium Data Encryption","id":"CVE-2019-4693","kev_date_added":null,"published":"2020-08-26"}],"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-17","vendors":["IBM"]},"summary":"Attackers can access sensitive data stored in URL parameters via logs or history, requiring an upgrade to IBM Guardium Data Encryption.","url":"https://insights.sbomify.com/CVE-2021-39020/"}