CVE-2019-5729: High severity splunk software development kit vulnerability
Published Mar 19, 2019
·Updated
Splunk-SDK-Python before 1.6.6 does not properly verify untrusted TLS server certificates, which could result in man-in-the-middle attacks.
Affected Software
2 affected componentsFixes available
Splunk Software Development Kit Python<1.6.6
pip/splunk-sdk<1.6.6
1.6.6
Event History
Mar 19, 2019
CVE Published
via MITRE·05:34 PM
Data Sourced
via MITRE·05:34 PM
Description
Mar 21, 2019
Data Sourced
via NVD·04:01 PM
DescriptionSeverityWeaknessAffected Software
Mar 25, 2019
Advisory Published
via GitHub·04:18 PM
Frequently Asked Questions
1
What is the severity of CVE-2019-5729?
CVE-2019-5729 has a high severity rating due to the potential for man-in-the-middle attacks.
2
How do I fix CVE-2019-5729?
To fix CVE-2019-5729, upgrade the Splunk SDK for Python to version 1.6.6 or later.
3
What is the impact of CVE-2019-5729?
The impact of CVE-2019-5729 is that attackers could intercept and manipulate communication between the client and the server.
4
Which versions are affected by CVE-2019-5729?
CVE-2019-5729 affects all versions of Splunk SDK for Python prior to version 1.6.6.
5
Is it safe to use CVE-2019-5729 in production?
It is not safe to use vulnerable versions affected by CVE-2019-5729 in production as it leaves systems open to security risks.