# CVE-2024-39302: Some bbb-record-core files installed with wrong file permission

> Attackers can exploit overly elevated file permissions in BigBlueButton core files to escalate privileges and access sensitive server information.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jun 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-5966-9hw8-q96q

## What is CVE-2024-39302?

CVE-2024-39302 is a low-severity vulnerability in bigbluebutton, published on 28 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

BigBlueButton is an open-source virtual classroom designed to help teachers teach and learners learn. An attacker may be able to exploit the overly elevated file permissions in the `/usr/local/bigbluebutton/core/vendor/bundle/ruby/2.7.0/gems/resque-2.6.0` directory with the goal of privilege escalation, potentially exposing sensitive information on the server. This issue has been patched in version(s) 2.6.18, 2.7.8 and 3.0.0-alpha.7.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2024-39302 being exploited?

There is no known exploitation of CVE-2024-39302 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-39302 is a low-severity vulnerability in bigbluebutton, published on 28 Jun 2024. 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-2024-39302 in the wild and no public exploit code.

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

## Sources

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

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