<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 22:31:56 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-210122</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-210122</link>
      <description>EUVD-2026-210122</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-210122</guid>
    </item>
    <item>
      <title>fkie_cve-2023-32691</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-32691</link>
      <description>&lt;p&gt;gost (GO Simple Tunnel) is a simple tunnel written in golang. Sensitive secrets such as passwords, token and API keys should be compared only using a constant-time comparison function. Untrusted input, sourced from a HTTP header, is compared directly with a secret. Since this comparison is not secure, an attacker can mount a side-channel timing attack to guess the password. As a workaround, this can be easily fixed using a constant time comparing function such as `crypto/subtle`&amp;#39;s `ConstantTimeCompare`.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;gost (GO Simple Tunnel) is a simple tunnel written in golang. Sensitive secrets such as passwords, token and API keys should be compared only using a constant-time comparison function. Untrusted input, sourced from a HTTP header, is compared directly with a secret. Since this comparison is not secure, an attacker can mount a side-channel timing attack to guess the password. As a workaround, this can be easily fixed using a constant time comparing function such as `crypto/subtle`&amp;#39;s `ConstantTimeCompare`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-32691</guid>
    </item>
    <item>
      <title>GHSA-qjrq-hm79-49ww — ginuerzh/gost vulnerable to Timing Attack</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-qjrq-hm79-49ww</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/ginuerzh/gost&lt;/p&gt;
&lt;p&gt;[Timing attacks](https://en.wikipedia.org/wiki/Timing_attack) occur when an attacker can guess a secret by observing a difference in processing time for valid and invalid inputs. Sensitive secrets such as passwords, token and API keys should be compared only using a constant-time comparision function.
More information on this attack type can be found in [this blog post](https://verboselogging.com/2012/08/20/a-timing-attack-in-action).&lt;/p&gt;
&lt;p&gt;# Root Cause Analysis&lt;/p&gt;
&lt;p&gt;In this case, the vulnerability occurs due to the following code.&lt;/p&gt;
&lt;p&gt;https://github.com/ginuerzh/gost/blob/1c62376e0880e4094bd3731e06bd4f7842638f6a/auth.go#L46-L46&lt;/p&gt;
&lt;p&gt;Here, a untrusted input, sourced from a HTTP header, is compared directly with a secret. 
Since, this comparision is not secure, an attacker can mount a side-channel timing attack to guess the password.&lt;/p&gt;
&lt;p&gt;# Remediation&lt;/p&gt;
&lt;p&gt;This can be easily fixed using a constant time comparing function such as `crypto/subtle`&amp;#39;s `ConstantTimeCompare`. 
An example fix can be found in https://github.com/runatlantis/atlantis/commit/48870911974adddaa4c99c8089e79b7d787fa820 Alternatively, one can apply the patch below&lt;/p&gt;
&lt;p&gt;```
From d18cff85e1a565f688f717fd8f2cacea62ff9dbf Mon Sep 17 00:00:00 2001
From: Porcupiney Hairs &amp;lt;porcupiney.hairs@protonmail.com&amp;gt;
Date: Sun, 7 May 2023 01:03:33 +0530
Subject: [PATCH] Fix : Timing attack&lt;/p&gt;
&lt;p&gt;---
 auth.go | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)&lt;/p&gt;
&lt;p&gt;diff --git a/auth.go b/auth.go
index 1be96e9..be13f23 100644
--- a/auth.go
+++ b/auth.go
@@ -2…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/ginuerzh/gost&lt;/p&gt;
&lt;p&gt;[Timing attacks](https://en.wikipedia.org/wiki/Timing_attack) occur when an attacker can guess a secret by observing a difference in processing time for valid and invalid inputs. Sensitive secrets such as passwords, token and API keys should be compared only using a constant-time comparision function.
More information on this attack type can be found in [this blog post](https://verboselogging.com/2012/08/20/a-timing-attack-in-action).&lt;/p&gt;
&lt;p&gt;# Root Cause Analysis&lt;/p&gt;
&lt;p&gt;In this case, the vulnerability occurs due to the following code.&lt;/p&gt;
&lt;p&gt;https://github.com/ginuerzh/gost/blob/1c62376e0880e4094bd3731e06bd4f7842638f6a/auth.go#L46-L46&lt;/p&gt;
&lt;p&gt;Here, a untrusted input, sourced from a HTTP header, is compared directly with a secret. 
Since, this comparision is not secure, an attacker can mount a side-channel timing attack to guess the password.&lt;/p&gt;
&lt;p&gt;# Remediation&lt;/p&gt;
&lt;p&gt;This can be easily fixed using a constant time comparing function such as `crypto/subtle`&amp;#39;s `ConstantTimeCompare`. 
An example fix can be found in https://github.com/runatlantis/atlantis/commit/48870911974adddaa4c99c8089e79b7d787fa820 Alternatively, one can apply the patch below&lt;/p&gt;
&lt;p&gt;```
From d18cff85e1a565f688f717fd8f2cacea62ff9dbf Mon Sep 17 00:00:00 2001
From: Porcupiney Hairs &amp;lt;porcupiney.hairs@protonmail.com&amp;gt;
Date: Sun, 7 May 2023 01:03:33 +0530
Subject: [PATCH] Fix : Timing attack&lt;/p&gt;
&lt;p&gt;---
 auth.go | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)&lt;/p&gt;
&lt;p&gt;diff --git a/auth.go b/auth.go
index 1be96e9..be13f23 100644
--- a/auth.go
+++ b/auth.go
@@ -2…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-qjrq-hm79-49ww</guid>
    </item>
    <item>
      <title>gsd-2023-32691</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-32691</link>
      <description>gsd-2023-32691</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-32691</guid>
    </item>
  </channel>
</rss>
