# CVE-2020-36627: Macaron i18n i18n.go redirect


- **Severity:** Medium 5.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 25 Dec 2022
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2020-36627, GHSA-jwrv-x6rx-8vfm, GO-2022-1187, UBUNTU-CVE-2020-36627

## What is CVE-2020-36627?

CVE-2020-36627 is a medium-severity vulnerability in Macaron i18n, published on 25 Dec 2022. 

### Official description

A vulnerability was found in Macaron i18n. It has been declared as problematic. Affected by this vulnerability is an unknown functionality of the file i18n.go. The manipulation leads to open redirect. The attack can be launched remotely. Upgrading to version 0.5.0 is able to address this issue. The name of the patch is 329b0c4844cc16a5a253c011b55180598e707735. It is recommended to upgrade the affected component. The identifier VDB-216745 was assigned to this vulnerability.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2020-36627?

3 open source packages ship an affected version, including github.com/go-macaron/i18n. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/go-macaron/i18n` | Go | All versions | 0.5.0 |
| `github.com/go-macaron/i18n` | Go | All versions | 0.5.0 |
| `github.com/go-macaron/i18n` | Go | All versions | 0.5.0 |

Products: Go-Macaron I18n.

## How do I fix CVE-2020-36627?

Upgrade github.com/go-macaron/i18n to 0.5.0 or later.

## Is CVE-2020-36627 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-36627 and fix it if it is affected.

What it is: CVE-2020-36627 is a medium-severity vulnerability in Macaron i18n, published on 25 Dec 2022. 
Exploitation: There is no known exploitation of CVE-2020-36627 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/go-macaron/i18n (Go): affected all versions; fixed in 0.5.0
- github.com/go-macaron/i18n (Go): affected all versions; fixed in 0.5.0
- github.com/go-macaron/i18n (Go): affected all versions; fixed in 0.5.0

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-2020-36627/ (Markdown: https://insights.sbomify.com/CVE-2020-36627/index.md)
```

## Sources

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

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