{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-25200 exists.","fix":"No fix has been published for CVE-2020-25200 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-25200 is a medium-severity vulnerability in n/a, published on 1 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-25200 and fix it if it is affected.\n\nWhat it is: CVE-2020-25200 is a medium-severity vulnerability in n/a, published on 1 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-25200 exists.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2020-25200/ (Markdown: https://insights.sbomify.com/CVE-2020-25200/index.md)","id":"CVE-2020-25200","markdown":"https://insights.sbomify.com/CVE-2020-25200/index.md","name":"CVE-2020-25200","record":{"aliases":["GHSA-9gwc-9rcr-pxmc"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Pritunl VPN server","requires_auth":"none","summary":"Attackers can enumerate valid VPN usernames by observing distinct HTTP error codes after repeated login attempts, potentially aiding targeted attacks.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pritunl","vendor":"pritunl"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-203","name":"Observable Discrepancy"}],"description":"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","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2020-09-06","github_poc":1,"max_poc_stars":4,"metasploit":0,"nuclei":1,"refs":[{"date":"2020-09-06T22:11:24Z","kind":"github_poc","ref":"https://github.com/lukaszstu/pritunl-CVE-2020-25200","stars":4,"title":"pritunl-CVE-2020-25200"},{"date":null,"kind":"nuclei","ref":"http/cves/2020/CVE-2020-25200.yaml","stars":null,"title":"Pritunl VPN Server 1.29.2145.25 - Username Enumeration"}],"tier":"weaponised"},"has_fix":false,"headline":"Information disclosure in n/a","id":"CVE-2020-25200","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":3,"next":{"headline":"Denial of service in HashiCorp Consul","id":"CVE-2020-25201"},"packages":[],"prev":{"headline":"Memory corruption in WECON Technology Co., Ltd LeviStudioU","id":"CVE-2020-25199"},"products":["n/a"],"published":"2020-10-01","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-11-18","vendors":["n/a"]},"summary":"Attackers can enumerate valid VPN usernames by observing distinct HTTP error codes after repeated login attempts, potentially aiding targeted attacks.","url":"https://insights.sbomify.com/CVE-2020-25200/"}