CVE-2023-4640 Set Logging Level Without Authentication
Unauthenticated attackers can modify logging levels in YugabyteDB Anywhere due to missing authorization checks in the controller.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2023-4640?
CVE-2023-4640 is a medium-severity missing authorization vulnerability in YugabyteDB Anywhere, published on 30 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
The controller responsible for setting the logging level does not include any authorization checks to ensure the user is authenticated. This can be seen by noting that it extends Controller rather than AuthenticatedController and includes no further checks. This issue affects YugabyteDB Anywhere: from 2.0.0 through 2.17.3
Weakness: CWE-284
Which versions are affected by CVE-2023-4640?
It affects 1 product.
Products include Yugabyte Yugabytedb.
How do I fix CVE-2023-4640?
No fix has been published for CVE-2023-4640 yet. Limit exposure of the affected software until one is available.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2023-4640 being exploited?
There is no known exploitation of CVE-2023-4640 in the wild and no public exploit code.
Other vulnerabilities in YugabyteDB Anywhere
Sources
Also known as GHSA-jqrr-cj4q-x8m4.