What is CVE-2018-25060?

CVE-2018-25060 is a high-severity security vulnerability in github.com/go-macaron/csrf (go), affecting versions < 0.0.0-20180426211050-dadd1711a617. It is fixed in 0.0.0-20180426211050-dadd1711a617.

How severe is CVE-2018-25060?

CVE-2018-25060 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of github.com/go-macaron/csrf are affected by CVE-2018-25060?

github.com/go-macaron/csrf (go) versions < 0.0.0-20180426211050-dadd1711a617 is affected.

Is there a fix for CVE-2018-25060?

Yes. CVE-2018-25060 is fixed in 0.0.0-20180426211050-dadd1711a617. Upgrade to this version or later.

Is CVE-2018-25060 exploitable, and should I be worried?

Whether CVE-2018-25060 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2018-25060 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2018-25060 in github.com/go-macaron/csrf

Q: How severe is CVE-2018-25060?

CVE-2018-25060 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of github.com/go-macaron/csrf are affected by CVE-2018-25060?

github.com/go-macaron/csrf (go) versions < 0.0.0-20180426211050-dadd1711a617 is affected.

Q: Is there a fix for CVE-2018-25060?

Yes. CVE-2018-25060 is fixed in 0.0.0-20180426211050-dadd1711a617. Upgrade to this version or later.

Q: Is CVE-2018-25060 exploitable, and should I be worried?

Whether CVE-2018-25060 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2018-25060 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2018-25060?

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

Summary

Macaron csrf missing encryption and has sensitive cookies in HTTP session without secure attribute

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 name of the patch is dadd1711a617000b70e5e408a76531b73187031c. It is recommended to apply a patch to fix this issue. VDB-217058 is the identifier assigned to this vulnerability.

Impact

CVE-2018-25060 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.0.0-20180426211050-dadd1711a617); upgrading removes the vulnerable code path.

Affected versions

github.com/go-macaron/csrf (< 0.0.0-20180426211050-dadd1711a617)

Security releases

github.com/go-macaron/csrf → 0.0.0-20180426211050-dadd1711a617 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2018-25060? CVE-2018-25060 is a high-severity security vulnerability in github.com/go-macaron/csrf (go), affecting versions < 0.0.0-20180426211050-dadd1711a617. It is fixed in 0.0.0-20180426211050-dadd1711a617.
How severe is CVE-2018-25060? CVE-2018-25060 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of github.com/go-macaron/csrf are affected by CVE-2018-25060? github.com/go-macaron/csrf (go) versions < 0.0.0-20180426211050-dadd1711a617 is affected.
Is there a fix for CVE-2018-25060? Yes. CVE-2018-25060 is fixed in 0.0.0-20180426211050-dadd1711a617. Upgrade to this version or later.
Is CVE-2018-25060 exploitable, and should I be worried? Whether CVE-2018-25060 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2018-25060 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2018-25060? Upgrade github.com/go-macaron/csrf to 0.0.0-20180426211050-dadd1711a617 or later.