Vulnerability Database · PyPI · kdcproxy · Version
kdcproxy 0.3.1
0.3.1 is affected by 2 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 1.1.0.
Critical 0 High 1 Medium 0 Low 0 Unrated 1
-
Released 22 Jul 2015
Licence MIT
Also known from other sources 2
Newer releases 6
Database updated 23/Oct/2026
Release and licence data published by PyPI. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
kdcproxy 0.3.1 vulnerabilities
2 vulnerabilities cover kdcproxy 0.3.1. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2015-5159: Improper Input Validation in kdcproxy | 7.5 high | 0.3.2 | 01 Nov 2018 |
| CVE-2015-5159: python-kdcproxy Denial of Service Vulnerability | N/A unrated | f274aa6787cb8b3ec1cc12c440a56665b7231882 | 30 Oct 2018 |
Looking for another version, or everything Vulert holds for kdcproxy?
Questions
About kdcproxy 0.3.1
Is kdcproxy 0.3.1 vulnerable?
Yes. 2 vulnerabilities in the Vulert database cover kdcproxy 0.3.1: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. The upgrade Vulert recommends is 1.1.0, and each entry above names the fixed version to move to.
Which version of kdcproxy should I use instead of 0.3.1?
1.1.0 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 0.3.1 the latest release of kdcproxy?
No. 0.3.1 was published 22 Jul 2015, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor kdcproxy for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the kdcproxy version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.