# CVE-2024-29291: Information disclosure in n/a

> Remote attackers may discover database credentials in log files if debugging is enabled and access controls are misconfigured.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-g8vg-q9j5-3vf5

## What is CVE-2024-29291?

CVE-2024-29291 is a vulnerability in n/a, published on 16 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in Laravel Framework 8 through 11 might allow a remote attacker to discover database credentials in storage/logs/laravel.log. NOTE: this is disputed by multiple third parties because the owner of a Laravel Framework installation can choose to have debugging logs, but needs to set the access control appropriately for the type of data that may be logged.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2024-29291?


## How do I fix CVE-2024-29291?

No fix has been published for CVE-2024-29291 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-29291 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-29291 exists.

Public exploit code:

- Laravel Framework 11 - Credential Leakage (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-29291 and fix it if it is affected.

What it is: CVE-2024-29291 is a vulnerability in n/a, published on 16 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-29291 exists.

Affected product: n/a. 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-2024-29291/ (Markdown: https://insights.sbomify.com/CVE-2024-29291/index.md)
```

## Sources

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

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