# CVE-2022-26945: Server-side request forgery in n/a

> Attackers can bypass security controls and access internal resources via protocol switching and endless redirects in the go-getter library.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2022-26945, MINI-23c8-pxjj-pw9f, MINI-24fr-2cjw-rfv9, MINI-2826-f5fx-cvj4, MINI-297j-98wq-cghx, MINI-2g95-qx7v-cfm5, MINI-2mmj-x549-mmm7, MINI-2q79-3j9c-4qg7, MINI-2ww9-7xrq-pwfj, MINI-2xmx-c283-6qq5, MINI-3797-4chw-7mcj, MINI-3g4p-xp27-g68x, MINI-488x-cv4j-w858, MINI-48r6-6922-7rqj, MINI-4ffc-fg8f-g9fg, MINI-4g85-8c3f-8jqj, MINI-4gxv-2h8h-7wp8, MINI-4m4x-mw4v-h797, MINI-4q9r-75jr-v9m5, MINI-524m-v2r3-7gm4, MINI-5696-gmrh-2396, MINI-57x8-p4cx-6859, MINI-5cr8-pgv5-xc7v, MINI-5fjj-w5cp-f783, MINI-5j8w-qm47-3cwv, MINI-5jpq-gcrr-xvhf, MINI-5xv2-2677-874m, MINI-69xf-x54v-j26v, MINI-6cxv-grm3-77jv, MINI-6g5h-xq39-gv6f, MINI-6hv6-h25x-p6cg, MINI-6jm7-2gcm-fg34, MINI-6pv6-m349-f22r, MINI-6v9p-c8vq-m9j2, MINI-6vf9-qf24-v49c, MINI-6w6q-g4fq-r6gc, MINI-6wp5-44gq-q7m9, MINI-7592-262c-gjvq, MINI-77wp-2g44-r8fp, MINI-79jp-wpg7-r64c, MINI-7cvr-x9fm-jhw3, MINI-7px5-qg43-rvf5, MINI-7vw3-p23c-c949, MINI-844g-pgq7-v3w8, MINI-85wm-gmv2-fqqq, MINI-86wh-vc2w-w49p, MINI-8jrg-47q3-h3rg, MINI-8pv5-48wj-765g, MINI-8rr9-82q7-4g28, MINI-8xcv-j486-7pvg, MINI-924m-863h-mg3h, MINI-9967-qm6f-33p6, MINI-99xj-j3vv-j559, MINI-9h48-m529-j478, MINI-9q5f-774f-8gw9, MINI-9qg5-q2f4-rjv4, MINI-9qqp-v854-pfx7, MINI-9w5w-q75g-v8hj, MINI-9wxm-x97m-22mg, MINI-9xjq-2h3v-7ghf, MINI-c2j3-78cg-m58h, MINI-cggq-jcjg-hj2w, MINI-cmff-m56h-cqcx, MINI-f32r-q3v8-f2vq, MINI-f57h-69qj-cr9m, MINI-f5rw-f9ff-rc37, MINI-f7m2-v5h5-6frx, MINI-ffmj-m3c2-2p6m, MINI-ffx6-x63r-8q8f, MINI-fgvv-4h3p-j3cf, MINI-fmqf-p7hm-5547, MINI-fqfh-7p4c-62vj, MINI-fqvx-r6qm-6xmj, MINI-fr7c-jhmx-ppm5, MINI-g5qx-9g82-mgg7, MINI-gm2m-xf6m-2qfv, MINI-gv3f-9wf7-wr2c, MINI-gv5q-f8wm-hmrq, MINI-h4vw-2mf5-35hc, MINI-hc4p-3pcm-6pfj, MINI-hcp7-8m67-h36q, MINI-hgrj-4hj4-94rc, MINI-hrw5-66hx-m973, MINI-hw79-8whx-rmmj, MINI-hwhq-fxp6-wqq4, MINI-j256-8j9j-jgp3, MINI-j5f4-gmpf-hwq8, MINI-j8vg-wq3h-rggr, MINI-jq4q-6w4r-c8ch, MINI-jrxg-77h6-g56w, MINI-m9p3-hc8x-gxwg, MINI-mj3f-5h29-mgg7, MINI-mmh4-4mq9-gw6v, MINI-p494-jxg3-v5qw, MINI-p5v3-p579-pxh3, MINI-p862-rq23-c5m6, MINI-p9q7-466g-8c23, MINI-pccx-qchw-95j8, MINI-pf2h-j4x9-277v, MINI-pgjc-mq3f-h4cg, MINI-pj62-5v3x-jx8w, MINI-prjq-mvvx-hq7j, MINI-pv37-jgfx-5hwv, MINI-pvv5-rq8w-h58v, MINI-pw5h-c9fj-m8c5, MINI-pwp5-43xg-f5mr, MINI-q5xf-97h8-jmrx, MINI-q6ch-j8f5-rxpr, MINI-qc24-95c7-rjvg, MINI-qcmv-c524-6jwf, MINI-qg44-c72j-2mw4, MINI-qmfv-4f2f-j3m5, MINI-qpwp-56p2-67x5, MINI-qqqv-x45f-f8rw, MINI-qvgc-qppf-f2hc, MINI-r2xv-qxjr-wvj4, MINI-r5x7-jfqr-2jwp, MINI-r679-xc6c-vm3j, MINI-r6c9-gfch-2qhh, MINI-r73c-wh2c-cf58, MINI-r9gh-fx45-g434, MINI-r9gj-pj4m-655q, MINI-rcp8-97cf-769j, MINI-rg4w-8gp8-mwxc, MINI-rmh8-7hc9-rfch, MINI-rqpr-qwqr-9j9g, MINI-rqr9-7v39-m6hw, MINI-rw87-fgj2-2jx9, MINI-rwfj-2wv2-x643, MINI-v2cf-5jhj-hp48, MINI-v34p-fvj3-v2mm, MINI-v6hj-mm5v-xwq3, MINI-v7m7-jf53-7m7w, MINI-v7p5-rq89-g7q7, MINI-vc35-53cw-878f, MINI-vhvc-fgc2-mrvx, MINI-vr4x-q28r-7qmc, MINI-vwc7-v4w6-98w9, MINI-w693-hvcm-q578, MINI-w7q7-qc7m-jxc7, MINI-whgj-pxrg-5294, MINI-wqm9-ph69-9v52, MINI-wqwp-g2fj-3qg9, MINI-wwjv-q9r6-j9fm, MINI-wwqj-v8j8-wj75, MINI-x63g-cxv8-p4jm, MINI-x7j4-j562-j5m3, MINI-x82h-7q9j-h23w, MINI-x946-53ww-pqp6, MINI-xcf8-j723-6r7h, MINI-xcrf-86q4-5qv8, MINI-xfrg-49qj-6jg5, MINI-xh35-4ff7-8264, MINI-xv6x-j6v2-vvcx, MINI-xwgf-32hq-v7wf, MINI-xwjf-q8q9-67w3, MINI-xxvr-f272-jfm9, UBUNTU-CVE-2022-26945

## What is CVE-2022-26945?

CVE-2022-26945 is a critical server-side request forgery vulnerability in n/a, published on 25 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

go-getter up to 1.5.11 and 2.0.2 allowed protocol switching, endless redirect, and configuration bypass via abuse of custom HTTP response header processing. Fixed in 1.6.1 and 2.1.0.

## Which versions are affected by CVE-2022-26945?

It affects 1 product.


Products: Hashicorp Go-Getter.

## How do I fix CVE-2022-26945?

Upgrade to a fixed version.

## Is CVE-2022-26945 being exploited?

There is no known exploitation of CVE-2022-26945 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2024-3817](https://insights.sbomify.com/CVE-2024-3817/): HashiCorp go-getter Vulnerable to Argument Injection When Fetching Remote Default Git Branches (critical 9.8)
- [CVE-2022-30321](https://insights.sbomify.com/CVE-2022-30321/): Path traversal in n/a (high 8.6)
- [CVE-2022-30322](https://insights.sbomify.com/CVE-2022-30322/): Denial of service in n/a (high 8.6)
- [CVE-2022-30323](https://insights.sbomify.com/CVE-2022-30323/): Denial of service in n/a (high 8.6)
- [CVE-2024-6257](https://insights.sbomify.com/CVE-2024-6257/): HashiCorp go-getter Vulnerable to Code Execution On Git Update Via Git Config Manipulation (high 8.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-26945 and fix it if it is affected.

What it is: CVE-2022-26945 is a critical server-side request forgery vulnerability in n/a, published on 25 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-26945 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-26945/ (Markdown: https://insights.sbomify.com/CVE-2022-26945/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-26945
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-26945
- OSV: https://osv.dev/vulnerability/CVE-2022-26945

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-26945/
Summaries are generated and may contain mistakes; the official description above is the record.
