LiveActive security incident?Get immediate response
CVE Record

CVE-2020-25200: Pritunl 1.29.2145.25 allows attackers to enumerate valid VPN usernames via a series of /auth/session login...

Pritunl 1.29.2145.25 allows attackers to enumerate valid VPN usernames via a series of /auth/session login attempts. Initially, the server will return error 401. However, if the username is valid, then after 20 login attempts, the server will start responding with error 400. Invalid usernames will receive error 401 indefinitely. Note: This has been disputed by the vendor as not a vulnerability. They argue that this is an intended design

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This CVE describes a username-enumeration behavior in Pritunl 1.29.2145.25. Repeated login attempts can reportedly make valid usernames produce a different error response than invalid ones. The vendor disputes that this is a vulnerability and says the behavior is intentional, so business urgency depends on exposure of the login surface.

Executive priority

Treat this as a low-urgency hardening item unless the Pritunl login surface is internet-exposed or targeted authentication probing is observed. Prioritize inventory, exposure reduction, and log review over emergency response.

Technical view

The reported issue concerns the /auth/session login flow. Sources say valid usernames eventually return HTTP 400 after repeated attempts, while invalid usernames continue returning HTTP 401. No CVSS, CWE, or complete affected-product metadata is provided in the bundle, and the vendor disputes the vulnerability classification.

Likely exposure

Potential exposure is limited to organizations running Pritunl 1.29.2145.25 with the relevant authentication endpoint reachable by untrusted users. The source bundle does not provide broader affected-version ranges.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The reported risk is account discovery, which could support phishing, credential stuffing, or targeted login attempts, but the provided sources do not establish compromise by itself.

Researcher notes

Evidence is limited and disputed. The CVE description identifies a response-difference username enumeration condition, but official metadata lacks CVSS, CWE, and normalized affected products. Do not claim active exploitation or a vendor patch from these sources alone.

Mitigation direction

  • Review Pritunl security guidance and release notes for vendor-supported direction.
  • Inventory exposed Pritunl instances and confirm whether version 1.29.2145.25 is present.
  • Restrict access to the Pritunl login surface where operationally feasible.
  • Monitor authentication logs for repeated failures against many usernames.
  • Apply vendor-supported updates if Pritunl identifies an applicable fix.

Validation and detection

  • Confirm the deployed Pritunl version from asset inventory or management records.
  • Determine whether /auth/session is reachable from the internet or untrusted networks.
  • Review logs for repeated failed login attempts and unusual status-code patterns.
  • Document the vendor-disputed status when recording risk acceptance or remediation decisions.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2020-25200 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.