CVE-2020-4071

Timing attack on django-basic-auth-ip-whitelist

LOW
2.4
CVSS Score
Published: June 24, 2020 at 12:15 PM UTC
Updated: June 17, 2026 at 03:19 AM UTC
2 products affected across 2 vendorsDjango Basic Auth IP WhitelistBasic Auth IP Whitelist Project Django Basic Auth IP Whitelist

Using django-basic-auth-ip-whitelist by tm-kn?

Get instant alerts when new vulnerabilities affect django-basic-auth-ip-whitelist - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
LOW2.4
Exploit prediction
EPSS 0.4%

Description

In django-basic-auth-ip-whitelist before 0.3.4, a potential timing attack exists on websites where the basic authentication is used or configured, i.e. BASIC_AUTH_LOGIN and BASIC_AUTH_PASSWORD is set. Currently the string comparison between configured credentials and the ones provided by users is performed through a character-by-character string comparison. This enables a possibility that attacker may time the time it takes the server to validate different usernames and password, and use this knowledge to work out the valid credentials. This attack is understood not to be realistic over the Internet. However, it may be achieved from within local networks where the website is hosted, e.g. from inside a data centre where a website's server is located. Sites protected by IP address whitelisting only are unaffected by this vulnerability. This vulnerability has been fixed on version 0.3.4 of django-basic-auth-ip-whitelist. Update to version 0.3.4 as soon as possible and change basic authentication username and password configured on a Django project using this package. A workaround without upgrading to version 0.3.4 is to stop using basic authentication and use the IP whitelisting component only. It can be achieved by not setting BASIC_AUTH_LOGIN and BASIC_AUTH_PASSWORD in Django project settings.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 0.3.4
Affected range stops below 0.3.4, so it looks safe — our inference, not a vendor statement
v < 0.3.4
Affected range stops below 0.3.4, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

CVSS

Attack Vector
PHYSICAL
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
LOW
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-208

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card