Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Users can access data via HTTP API without any authentication #15389

Open
tennix opened this issue Mar 15, 2020 · 4 comments
Open

Users can access data via HTTP API without any authentication #15389

tennix opened this issue Mar 15, 2020 · 4 comments
Labels
security Everything related with security

Comments

@tennix
Copy link
Member

tennix commented Mar 15, 2020

According to tidb-ctl documentation https://github.com/pingcap/tidb-ctl/blob/master/doc/tidb-ctl.md, users can access data via tidb-server HTTP API without authentication. This is a security vulnerability.

If users expose TiDB HTTP API unintentionally, or even internal non-authorized users can access TiDB data without requiring TiDB's user and password.

CockroachDB has the same issue but fixed in newer versions https://www.cockroachlabs.com/docs/advisories/a42567.html

We might need to fix this too.

@tennix tennix added the security Everything related with security label Mar 15, 2020
@lysu
Copy link
Contributor

lysu commented Mar 16, 2020

@tennix after #15137, http ap user(include tidb-ctl) must provide cert/key and acess https after using cluster-allow-cn

@frank-dspeed
Copy link

frank-dspeed commented Mar 20, 2020

@tennix @lysu you forgot to close this issue after merge :)

@lysu
Copy link
Contributor

lysu commented Mar 22, 2020

Thanks @frank-dspeed 😄 , I had discussed more about this with @tennix offline, after #15137 we could solve a part of the problem when the user enable HTTPS, but maybe need more improvement to keep safe for user that didn't enable https or do more fine-grain control in http api later

@dveeden
Copy link
Contributor

dveeden commented Jul 19, 2021

Looks like #12317 is more or less the same issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
security Everything related with security
Projects
None yet
Development

No branches or pull requests

4 participants