CVE-2020-25200 json
Pritunl 1.29.2145.25 allows attackers to enumerate valid VPN usernames via a series of /auth/session login attempts.
published 6y ago modified 4mo ago also EUVD-2020-17891
- cvss
- 5.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 7.5%
- EPSS 7.5% chance of exploitation in 30 days, percentile 94%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
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
Is CVE-2020-25200 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
7.47% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Nuclei template Pritunl VPN Server 1.29.2145.25 - Username Enumeration nuclei detection template
- github.com https://github.com/lukaszstu/pritunl/blob/master/CVE-2020-25200 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-203 Observable Discrepancy
References
-
github.com
/lukaszstu/pritunl/blob/master/CVE-2020-25200
exploit, third-party-advisory
-
pritunl.com
vendor-advisory
-
pritunl.com
/security
vendor-advisory
Sources
- CVE List CVE-2020-25200
- NVD CVE-2020-25200
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.