{"answers":{"affected":"1 open source package ship an affected version, including golang.org/x/crypto.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-30636 exists.","fix":"Upgrade golang.org/x/crypto to 0.0.0-20220525230936-793ad666bf5e or later.","what":"CVE-2022-30636 is a high-severity path traversal vulnerability in golang.org/x/crypto/acme/autocert, published on 2 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-30636 and fix it if it is affected.\n\nWhat it is: CVE-2022-30636 is a high-severity path traversal vulnerability in golang.org/x/crypto/acme/autocert, published on 2 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-30636 exists.\n\nAffected packages and fixed versions:\n- golang.org/x/crypto (Go): affected all versions; fixed in 0.0.0-20220525230936-793ad666bf5e\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-2022-30636/ (Markdown: https://insights.sbomify.com/CVE-2022-30636/index.md)","id":"CVE-2022-30636","markdown":"https://insights.sbomify.com/CVE-2022-30636/index.md","name":"CVE-2022-30636","record":{"aliases":["CLEANSTART-2026-GE07592","CLEANSTART-2026-QN19137","DEBIAN-CVE-2022-30636","GO-2024-2961","MINI-hm94-v333-g5qh"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Go crypto library","requires_auth":"none","summary":"An attacker can read arbitrary files on Windows systems if they end with the specific suffix +http-01 due to path traversal in the ACME autocert cache.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Go","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[],"description":"httpTokenCacheKey uses path.Base to extract the expected HTTP-01 token value to lookup in the DirCache implementation. On Windows, path.Base acts differently to filepath.Base, since Windows uses a different path separator (\\ vs. /), allowing a user to provide a relative path, i.e. .well-known/acme-challenge/..\\..\\asd becomes ..\\..\\asd. The extracted path is then suffixed with +http-01, joined with the cache directory, and opened. Since the controlled path is suffixed with +http-01 before opening, the impact of this is significantly limited, since it only allows reading arbitrary files on the system if and only if they have this suffix.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Limited directory traversal vulnerability on Windows in golang.org/x/crypto","id":"CVE-2022-30636","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"path_traversal","year":"2022"},"n_packages":1,"n_references":3,"next":{"headline":"Adobe Illustrator Font Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability","id":"CVE-2022-30637"},"packages":[{"ecosystem":"Go","fixed":["0.0.0-20220525230936-793ad666bf5e"],"introduced":["0"],"last_affected":[],"package":"golang.org/x/crypto","purl":"pkg:golang/golang.org/x/crypto","source":"GO-2024-2961"}],"prev":{"headline":"Stack exhaustion when decoding certain messages in encoding/gob","id":"CVE-2022-30635"},"products":["golang.org/x/crypto/acme/autocert"],"published":"2024-07-02","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-07","vendors":["golang.org/x/crypto"]},"summary":"An attacker can read arbitrary files on Windows systems if they end with the specific suffix +http-01 due to path traversal in the ACME autocert cache.","url":"https://insights.sbomify.com/CVE-2022-30636/"}