{"answers":{"affected":"2 open source packages ship an affected version, including github.com/wal-g/wal-g. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-38599 in the wild and no public exploit code.","fix":"Upgrade github.com/wal-g/wal-g to 1.1 or later.","what":"CVE-2021-38599 is a high-severity vulnerability in n/a, published on 12 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-38599 and fix it if it is affected.\n\nWhat it is: CVE-2021-38599 is a high-severity vulnerability in n/a, published on 12 Aug 2021. 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-2021-38599 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/wal-g/wal-g (Go): affected all versions; fixed in 1.1\n- github.com/wal-g/wal-g (Go): affected all versions; fixed in 1.1\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-38599/ (Markdown: https://insights.sbomify.com/CVE-2021-38599/index.md)","id":"CVE-2021-38599","markdown":"https://insights.sbomify.com/CVE-2021-38599/index.md","name":"CVE-2021-38599","record":{"aliases":["GHSA-vrmr-f2qh-3hhf"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Go backup library","requires_auth":"none","summary":"WAL-G silently uploads unencrypted backups when using non-libsodium builds, exposing sensitive data to attackers.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"wal-g","vendor":"wal-g_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-754","name":"Improper Check for Unusual or Exceptional Conditions"}],"description":"WAL-G before 1.1, when a non-libsodium build (e.g., one of the official binary releases published as GitHub Releases) is used, silently ignores the libsodium encryption key and uploads cleartext backups. This is arguably a Principle of Least Surprise violation because \"the user likely wanted to encrypt all file activity.\"","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Improper use of cryptographic key in wal-g","id":"CVE-2021-38599","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"weak_cryptography","year":"2021"},"n_packages":2,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2021-38602"},"packages":[{"ecosystem":"Go","fixed":["1.1"],"introduced":["0"],"last_affected":[],"package":"github.com/wal-g/wal-g","purl":null,"source":"GHSA-vrmr-f2qh-3hhf"},{"ecosystem":"Go","fixed":["1.1"],"introduced":["0"],"last_affected":[],"package":"github.com/wal-g/wal-g","purl":"pkg:golang/github.com/wal-g/wal-g","source":"GHSA-vrmr-f2qh-3hhf"}],"prev":{"headline":"OpenStack Neutron vulnerable to hardware address impersonation","id":"CVE-2021-38598"},"products":["n/a"],"published":"2021-08-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-04","vendors":["n/a"]},"summary":"WAL-G silently uploads unencrypted backups when using non-libsodium builds, exposing sensitive data to attackers.","url":"https://insights.sbomify.com/CVE-2021-38599/"}