Skip to content
Fencer Intel
high 7.5

CVE-2013-10005 json

Infinite loop in github.com/btcsuite/go-socks

published 5y ago modified 4mo ago also GHSA-gxgj-xjcw-fv9p , GO-2020-0024 , EUVD-2022-7640

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 57%
public exploits
0
none known

Summary

The RemoteAddr and LocalAddr methods on the returned net.Conn may call themselves, leading to an infinite loop which will crash the program due to a stack overflow.

Patch / fix

  • go github.com/btcsuite/go-socks 0.0.0-20130808000456-233bccbb1abe
  • go github.com/btcsuitereleases/go-socks 0.0.0-20130808000456-233bccbb1abe
  • github.com/btcsuite/go-socks github.com/btcsuite/go-socks 0.0.0-20130808000456-233bccbb1abe
  • github.com/btcsuitereleases/go-socks github.com/btcsuitereleases/go-socks 0.0.0-20130808000456-233bccbb1abe

Is CVE-2013-10005 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.83% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CISA ADP 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
go github.com/btcsuite/go-socks
<0.0.0-20130808000456-233bccbb1abe
0.0.0-20130808000456-233bccbb1abe
go github.com/btcsuitereleases/go-socks
<0.0.0-20130808000456-233bccbb1abe
0.0.0-20130808000456-233bccbb1abe

Affected products

  • github.com/btcsuite/go-socks github.com/btcsuite/go-socks
  • github.com/btcsuitereleases/go-socks github.com/btcsuitereleases/go-socks

Classification

Weakness
  • CWE-835 Loop with Unreachable Exit Condition

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.