# CVE-2018-25060: Macaron csrf csrf.go missing secure attribute

> The Macaron CSRF library fails to set the Secure attribute on cookies, allowing potential interception of CSRF tokens over unencrypted connections.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Dec 2022
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-25060, GHSA-hhxg-px5h-jc32, GO-2022-1213, UBUNTU-CVE-2018-25060

## What is CVE-2018-25060?

CVE-2018-25060 is a low-severity vulnerability in Macaron csrf, published on 30 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in Macaron csrf and classified as problematic. Affected by this issue is some unknown functionality of the file csrf.go. The manipulation of the argument Generate leads to sensitive cookie without secure attribute. The attack may be launched remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The patch is identified as dadd1711a617000b70e5e408a76531b73187031c. It is recommended to apply a patch to fix this issue. VDB-217058 is the identifier assigned to this vulnerability.

Weakness: CWE-311 (Missing Encryption of Sensitive Data), CWE-614 (Sensitive Cookie in HTTPS Session Without 'Secure' Attribute)

## Which versions are affected by CVE-2018-25060?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/go-macaron/csrf` | Go | All versions | 0.0.0-20180426211050-dadd1711a617 |
| `github.com/go-macaron/csrf` | Go | All versions | 0.0.0-20180426211050-dadd1711a617 |
| `github.com/go-macaron/csrf` | Go | All versions | 0.0.0-20180426211050-dadd1711a617 |

Products: Go-Macaron Csrf.

## How do I fix CVE-2018-25060?

Upgrade github.com/go-macaron/csrf to 0.0.0-20180426211050-dadd1711a617 or later.

## Is CVE-2018-25060 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25060 and fix it if it is affected.

What it is: CVE-2018-25060 is a low-severity vulnerability in Macaron csrf, published on 30 Dec 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-2018-25060 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/go-macaron/csrf (Go): affected all versions; fixed in 0.0.0-20180426211050-dadd1711a617
- github.com/go-macaron/csrf (Go): affected all versions; fixed in 0.0.0-20180426211050-dadd1711a617
- github.com/go-macaron/csrf (Go): affected all versions; fixed in 0.0.0-20180426211050-dadd1711a617

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

## Sources

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

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