# 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.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Aug 2023
- **Updated:** 1 Oct 2024
- **Also known as:** GHSA-jqrr-cj4q-x8m4

## 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 (Improper Access Control)

## Which versions are affected by CVE-2023-4640?

It affects 1 product.


Products: 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.

## 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

- [CVE-2022-37397](https://insights.sbomify.com/CVE-2022-37397/): The software is vulnerable when using LDAP-based authentication in YCQL with Microsoft’s Active Directory (high 8.3)
- [CVE-2024-41435](https://insights.sbomify.com/CVE-2024-41435/): Memory corruption in n/a (high 7.5)
- [CVE-2023-0575](https://insights.sbomify.com/CVE-2023-0575/): Remote Code Execution (high 7.2)
- [CVE-2023-6002](https://insights.sbomify.com/CVE-2023-6002/): Log Injection (medium 6.5)
- [CVE-2023-6001](https://insights.sbomify.com/CVE-2023-6001/): Prometheus Metrics Accessible Pre-Authentication (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-4640 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2023-4640 in the wild and no public exploit code.

Affected product: YugabyteDB Anywhere. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-4640/ (Markdown: https://insights.sbomify.com/CVE-2023-4640/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-4640
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-4640
- OSV: https://osv.dev/vulnerability/CVE-2023-4640

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-4640/
Summaries are generated and may contain mistakes; the official description above is the record.