CVE-2020-11710
First published: Sun Apr 12 2020(Updated: )
** DISPUTED ** An issue was discovered in docker-kong (for Kong) through 2.0.3. The admin API port may be accessible on interfaces other than 127.0.0.1. NOTE: The vendor argue that this CVE is not a vulnerability because it has an inaccurate bug scope and patch links. “1) Inaccurate Bug Scope - The issue scope was on Kong's docker-compose template, and not Kong's docker image itself. In reality, this issue is not associated with any version of the Kong gateway. As such, the description stating ‘An issue was discovered in docker-kong (for Kong) through 2.0.3.’ is incorrect. This issue only occurs if a user decided to spin up Kong via docker-compose without following the security documentation. The docker-compose template is meant for users to quickly get started with Kong, and is meant for development purposes only. 2) Incorrect Patch Links - The CVE currently points to a documentation improvement as a “Patch” link: https://github.com/Kong/docs.konghq.com/commit/d693827c32144943a2f45abc017c1321b33ff611.This link actually points to an improvement Kong Inc made for fool-proofing. However, instructions for how to protect the admin API were already well-documented here: https://docs.konghq.com/2.0.x/secure-admin-api/#network-layer-access-restrictions , which was first published back in 2017 (as shown in this commit: https://github.com/Kong/docs.konghq.com/commit/e99cf875d875dd84fdb751079ac37882c9972949) Lastly, the hyperlink to https://github.com/Kong/kong (an unrelated Github Repo to this issue) on the Hyperlink list does not include any meaningful information on this topic.”
Credit: cve@mitre.org cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Konghq Docker-kong | <=2.0.3 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is CVE-2020-11710?
CVE-2020-11710 is an issue discovered in docker-kong (for Kong) through version 2.0.3, where the admin API port may be accessible on interfaces other than 127.0.0.1.
What is the severity of CVE-2020-11710?
CVE-2020-11710 has a severity keyword of 'critical' and a severity value of 9.8.
How can I fix CVE-2020-11710?
To fix CVE-2020-11710, update docker-kong to version 2.0.4 or later.
Are there any references for CVE-2020-11710?
Yes, you can find references for CVE-2020-11710 on the following links: [GitHub Commit 1](https://github.com/Kong/docker-kong/commit/dfa095cadf7e8309155be51982d8720daf32e31c), [GitHub Commit 2](https://github.com/Kong/docs.konghq.com/commit/d693827c32144943a2f45abc017c1321b33ff611), [GitHub Commit 3](https://github.com/Kong/docs.konghq.com/commit/e99cf875d875dd84fdb751079ac37882c9972949)
Is CVE-2020-11710 a disputed vulnerability?
Yes, CVE-2020-11710 is disputed by the vendor due to inaccurate bug scope and patch links.
- collector/nvd-index
- agent/type
- agent/references
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/remedy
- agent/severity
- agent/last-modified-date
- agent/author
- agent/status
- agent/softwarecombine
- agent/description
- agent/first-publish-date
- agent/event
- agent/tags
- status/disputed
- vendor/konghq
- canonical/konghq docker-kong
- version/konghq docker-kong/2.0.3