# GHSA-g3j5-mpp2-2fqm: symfont/process typosquatting malware spoofs symfony/process

> Attackers can execute arbitrary code by tricking developers into installing a malicious typosquatted Composer package instead of the legitimate symfony/process library.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Jan 2023

## What is GHSA-g3j5-mpp2-2fqm?

GHSA-g3j5-mpp2-2fqm is a vulnerability in symfont/process, published on 26 Jan 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

In September 2021, security researchers discovered a malicious Composer package called `symfont/process`, a typosquat targeting users of `symfony/process`. The malicious package has since been removed from Packagist.

## Which versions are affected by GHSA-g3j5-mpp2-2fqm?

2 open source packages ship an affected version, including symfont/process.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `symfont/process` | Packagist | All versions | None |
| `symfont/process` | Packagist | All versions | None |

## How do I fix GHSA-g3j5-mpp2-2fqm?

No fix has been published for GHSA-g3j5-mpp2-2fqm yet. Limit exposure of the affected software until one is available.

## Is GHSA-g3j5-mpp2-2fqm being exploited?

There is no known exploitation of GHSA-g3j5-mpp2-2fqm in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-g3j5-mpp2-2fqm and fix it if it is affected.

What it is: GHSA-g3j5-mpp2-2fqm is a vulnerability in symfont/process, published on 26 Jan 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-g3j5-mpp2-2fqm in the wild and no public exploit code.

Affected packages and fixed versions:
- symfont/process (Packagist): affected all versions; no fix listed
- symfont/process (Packagist): affected all versions; no fix listed

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-g3j5-mpp2-2fqm/ (Markdown: https://insights.sbomify.com/GHSA-g3j5-mpp2-2fqm/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-g3j5-mpp2-2fqm

---
From sbomify Insights: https://insights.sbomify.com/GHSA-g3j5-mpp2-2fqm/
Summaries are generated and may contain mistakes; the official description above is the record.