CVE-2017-14711
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 · uneditedThe Kickbase GmbH "Kickbase Bundesliga Manager" app before 2.2.1 -- aka kickbase-bundesliga-manager/id678241305 -- for iOS is vulnerable to a credentials leak due to transmitting a username and password in cleartext from client to server during registration and authentication.
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 Kickbase Bundesliga Manager iOS app before version 2.2.1 transmits user credentials (username and password) in cleartext during registration and authentication processes. This allows network attackers to intercept sensitive authentication data as it travels from the client app to the server.
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< 2.2.1CVSS 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.
-
Confirm Kickbase Bundesliga Manager app is installedOpen the iOS device Settings app, navigate to General > iPhone Storage (or Device Management on older iOS), and look for the Kickbase Bundesliga Manager app in the list of installed applicationsAffected if The app is present on the device
-
Check the installed app versionOpen the App Store app, search for 'Kickbase Bundesliga Manager', tap on the app, and view the version number displayed under the app name. Alternatively, check via iPhone Storage view in SettingsAffected if The version shown is lower than 2.2.1 (for example, 2.2.0, 2.1.x, etc.)
-
Inspect network traffic for credential transmissionConfigure a network proxy (such as Charles Proxy or Burp Suite) on a computer connected to the same network as the iOS device, install the proxy certificate on the iOS device to enable SSL interception, then launch the Kickbase app and perform a login or registration while monitoring the proxy for outgoing connectionsAffected if Authentication requests (containing username/password fields) are sent over plain HTTP instead of HTTPS, or the app fails to establish TLS connections to authentication endpoints
-
Verify TLS certificate validationDuring the network inspection above, observe whether the app properly validates server certificates when connecting, or check if the app accepts invalid/self-signed certificates without warningAffected if The app disables SSL certificate validation or does not verify server identity, allowing man-in-the-middle attacks
A user is affected if the Kickbase Bundesliga Manager app version is below 2.2.1 and the app transmits login credentials over unencrypted HTTP or fails to properly validate TLS certificates during authentication.
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 data2.2.1
Implement TLS/SSL encryption (HTTPS) for all authentication endpoints and ensure the app properly validates server certificates to prevent man-in-the-middle attacks during credential transmission.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14711 — 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-2017-14711 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