CVE-2020-36569 Authentication bypass in github.com/nanobox-io/golang-nanoauth

Critical 9.1 Published Updated

Attackers can bypass authentication in the golang-nanoauth library if the server is configured with an empty token.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2020-36569?

CVE-2020-36569 is a critical authentication bypass vulnerability in github.com/nanobox-io/golang-nanoauth, published on 27 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

Authentication is globally bypassed in github.com/nanobox-io/golang-nanoauth between v0.0.0-20160722212129-ac0cc4484ad4 and v0.0.0-20200131131040-063a3fb69896 if ListenAndServe is called with an empty token.

Weakness: CWE-287

Which versions are affected by CVE-2020-36569?

3 open source packages ship an affected version, including github.com/nanobox-io/golang-nanoauth. It affects 1 product.

PackageAffectedFixed in
github.com/nanobox-io/golang-nanoauth GoFrom 0.0.0-20160722212129-ac0cc4484ad40.0.0-20200131131040-063a3fb69896
github.com/nanobox-io/golang-nanoauth GoFrom 0.0.0-20160722212129-ac0cc4484ad40.0.0-20200131131040-063a3fb69896
github.com/nanobox-io/golang-nanoauth GoFrom 0.0.0-20160722212129-ac0cc4484ad40.0.0-20200131131040-063a3fb69896

Products include Digitalocean Golang-Nanoauth.

How do I fix CVE-2020-36569?

Upgrade github.com/nanobox-io/golang-nanoauth to 0.0.0-20200131131040-063a3fb69896 or later.

Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.

Is CVE-2020-36569 being exploited?

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

Sources

Also known as GHSA-hrm3-3xm6-x33h, GO-2020-0004.

Is CVE-2020-36569 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free