{"answers":{"affected":"3 open source packages ship an affected version, including go.elastic.co/apm. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-22133 in the wild and no public exploit code.","fix":"Upgrade go.elastic.co/apm to 1.11.0 or later.","what":"CVE-2021-22133 is a low-severity vulnerability in Elastic APM Agent for Go, published on 10 Feb 2021. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-22133 and fix it if it is affected.\n\nWhat it is: CVE-2021-22133 is a low-severity vulnerability in Elastic APM Agent for Go, published on 10 Feb 2021. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-22133 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- go.elastic.co/apm (Go): affected all versions; fixed in 1.11.0\n- go.elastic.co/apm (Go): affected all versions; fixed in 1.11.0\n- go.elastic.co/apm (Go): affected all versions; fixed in 1.11.0\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-22133/ (Markdown: https://insights.sbomify.com/CVE-2021-22133/index.md)","id":"CVE-2021-22133","markdown":"https://insights.sbomify.com/CVE-2021-22133/index.md","name":"CVE-2021-22133","record":{"aliases":["GHSA-qqc5-rgcc-cjqh","GO-2022-0706"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Go APM agent","requires_auth":"high_privilege","summary":"An attacker can view sensitive HTTP headers in logs during application panics because the Go APM agent fails to sanitize them.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"apm_agent","vendor":"elastic"}],"cvss":{"score":2.4,"severity":"low","source":"nvd","vector":"CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"The Elastic APM agent for Go versions before 1.11.0 can leak sensitive HTTP header information when logging the details during an application panic. Normally, the APM agent will sanitize sensitive HTTP header details before sending the information to the APM server. During an application panic it is possible the headers will not be sanitized before being sent.","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":"Information Disclosure in go.elastic.co/apm","id":"CVE-2021-22133","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"information_disclosure","year":"2021"},"n_packages":3,"n_references":1,"next":{"headline":"Exposure of Sensitive Information to an Unauthorized Actor","id":"CVE-2021-22134"},"packages":[{"ecosystem":"Go","fixed":["1.11.0"],"introduced":["0"],"last_affected":[],"package":"go.elastic.co/apm","purl":null,"source":"GHSA-qqc5-rgcc-cjqh"},{"ecosystem":"Go","fixed":["1.11.0"],"introduced":["0"],"last_affected":[],"package":"go.elastic.co/apm","purl":"pkg:golang/go.elastic.co/apm","source":"GHSA-qqc5-rgcc-cjqh"},{"ecosystem":"Go","fixed":["1.11.0"],"introduced":["0"],"last_affected":[],"package":"go.elastic.co/apm","purl":"pkg:golang/go.elastic.co/apm","source":"GO-2022-0706"}],"prev":{"headline":"Insufficiently Protected Credentials in Elasticsearch","id":"CVE-2021-22132"},"products":["Elastic APM Agent for Go"],"published":"2021-02-10","related":[{"cvss_score":7.8,"headline":"APM Java Agent Local Privilege Escalation","id":"CVE-2021-37941","kev_date_added":null,"published":"2021-12-08"},{"cvss_score":7.2,"headline":"Elastic APM agent for Python client CGI proxy redirection flaw","id":"CVE-2019-7617","kev_date_added":null,"published":"2019-08-22"}],"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":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"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-03","vendors":["Elastic"]},"summary":"An attacker can view sensitive HTTP headers in logs during application panics because the Go APM agent fails to sanitize them.","url":"https://insights.sbomify.com/CVE-2021-22133/"}