# GHSA-fgrx-4637-fcf5: fuel/core Crypt encryption compromised.

> Weak encryption in FuelPHP core allows attackers to decrypt sensitive data using GPU power, compromising confidentiality.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 May 2024

## What is GHSA-fgrx-4637-fcf5?

GHSA-fgrx-4637-fcf5 is a vulnerability in fuel/core, published on 15 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In fuel/core versions pior to 1.8.1, with the right knowledge, code, and GPU calculation power, Crypt encryption can be broken in minutes.

## Which versions are affected by GHSA-fgrx-4637-fcf5?

2 open source packages ship an affected version, including fuel/core.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `fuel/core` | Packagist | All versions | 1.8.1 |
| `fuel/core` | Packagist | All versions | 1.8.1 |

## How do I fix GHSA-fgrx-4637-fcf5?

Upgrade fuel/core to 1.8.1 or later.

## Is GHSA-fgrx-4637-fcf5 being exploited?

There is no known exploitation of GHSA-fgrx-4637-fcf5 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-fgrx-4637-fcf5 and fix it if it is affected.

What it is: GHSA-fgrx-4637-fcf5 is a vulnerability in fuel/core, published on 15 May 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 GHSA-fgrx-4637-fcf5 in the wild and no public exploit code.

Affected packages and fixed versions:
- fuel/core (Packagist): affected all versions; fixed in 1.8.1
- fuel/core (Packagist): affected all versions; fixed in 1.8.1

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/GHSA-fgrx-4637-fcf5/ (Markdown: https://insights.sbomify.com/GHSA-fgrx-4637-fcf5/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-fgrx-4637-fcf5

---
From sbomify Insights: https://insights.sbomify.com/GHSA-fgrx-4637-fcf5/
Summaries are generated and may contain mistakes; the official description above is the record.