CVE-2020-11710

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.

• https://github.com/Kong/docker-kong/commit/dfa095cadf7e8309155be51982d8720daf32e31cPatch, Third Party Advisory
• https://github.com/Kong/docs.konghq.com/commit/d693827c32144943a2f45abc017c1321b33ff611Patch, Third Party Advisory
• https://github.com/Kong/docs.konghq.com/commit/e99cf875d875dd84fdb751079ac37882c9972949
• https://github.com/Kong/kongThird Party Advisory
• https://github.com/Kong/docker-kong/commit/dfa095cadf7e8309155be51982d8720daf32e31cPatch, Third Party Advisory
• https://github.com/Kong/docs.konghq.com/commit/d693827c32144943a2f45abc017c1321b33ff611Patch, Third Party Advisory
• https://github.com/Kong/docs.konghq.com/commit/e99cf875d875dd84fdb751079ac37882c9972949
• https://github.com/Kong/kongThird Party Advisory

Published

Apr 12, 2020

Last Modified

Jun 17, 2026

Status

Modified

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2020-11705An issue was discovered in ProVide (formerly zFTPServer) thr…9.8
• CVE-2020-11706An issue was discovered in ProVide (formerly zFTPServer) thr…8.8
• CVE-2020-11707An issue was discovered in ProVide (formerly zFTPServer) thr…8.8
• CVE-2020-11708An issue was discovered in ProVide (formerly zFTPServer) thr…9.8
• CVE-2020-11709cpp-httplib through 0.5.8 does not filter \r\n in parameters…7.5
• CVE-2020-1171A remote code execution vulnerability exists in Visual Studi…8.8
• CVE-2020-11711An issue was discovered in Stormshield SNS 3.8.0. Authentica…4.8
• CVE-2020-11712Open Upload through 0.4.3 allows XSS via index.php?action=u …6.1
• CVE-2020-11713wolfSSL 4.3.0 has mulmod code in wc_ecc_mulmod_ex in ecc.c t…7.5
• CVE-2020-11714eten PSG-6528VM 1.1 devices allow XSS via System Contact or …5.4
• CVE-2020-11715Panasonic P99 devices through 2020-04-10 have Incorrect Acce…9.8
• CVE-2020-11716Panasonic P110, Eluga Z1 Pro, Eluga X1, and Eluga X1 Pro dev…9.8