Software Development KitApplication · Splunk
CVE-2019-5729
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSplunk-SDK-Python before 1.6.6 does not properly verify untrusted TLS server certificates, which could result in man-in-the-middle attacks.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Splunk-SDK-Python before version 1.6.6 fails to properly validate TLS/SSL server certificates during HTTPS connections, allowing an attacker positioned between the client and server to intercept sensitive data by presenting a fraudulent certificate.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Software Development KitApplication
< 1.6.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Splunk-SDK-Python versionRun 'pip show splunk-sdk' or 'pip list | grep splunk' to see the installed versionAffected if The installed version is lower than 1.6.6
-
Inspect code for SSL verification bypassSearch your codebase for 'verify=False', 'ssl._create_unverified_context()', or 'context.check_hostname = False' when using the Splunk SDKAffected if SSL verification is explicitly disabled in code that uses the Splunk SDK for HTTPS connections
-
Check SDK client initialization for verification settingsReview any Splunk SDK client instantiation for 'verify' parameter set to False, or SSL context configuration that disables certificate validationAffected if The SDK client is initialized with verify=False or equivalent SSL verification disabling option
-
Identify applications using the vulnerable SDKSearch project dependencies (requirements.txt, setup.py, Pipfile) for 'splunk-sdk' or 'splunklib' and note the version constraintAffected if The project depends on splunk-sdk version < 1.6.6
A user is affected if their environment has Splunk-SDK-Python installed with version lower than 1.6.6 AND uses it to make HTTPS connections, particularly if SSL verification is disabled in the implementation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data1.6.6
Upgrade Splunk-SDK-Python to version 1.6.6 or later which includes proper certificate verification logic.
Fix this in Software Development Kit
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5729 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-5729 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data