GHSA-73qr-pfmq-6rp8 Embedded malware in coa
Not scored
Published
Check this codebase for GHSA-73qr-pfmq-6rp8 and fix it if it is affected.
What it is: GHSA-73qr-pfmq-6rp8 is a vulnerability in coa, published on 4 Nov 2021. 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-73qr-pfmq-6rp8 in the wild and no public exploit code.
Affected packages and fixed versions:
- coa (npm): affected all versions; no fix listed
- coa (npm): 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-73qr-pfmq-6rp8/ (Markdown: https://insights.sbomify.com/GHSA-73qr-pfmq-6rp8/index.md)
Malicious code in the coa npm package allows attackers to fully compromise systems, requiring immediate removal and credential rotation.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is GHSA-73qr-pfmq-6rp8?
GHSA-73qr-pfmq-6rp8 is a vulnerability in coa, published on 4 Nov 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
The npm package
coa had versions published with malicious code. Users of affected versions (2.0.3 and above) should downgrade to 2.0.2 as soon as possible and check their systems for suspicious activity. See this issue for details as they unfold.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.Which versions are affected by GHSA-73qr-pfmq-6rp8?
2 open source packages ship an affected version, including coa.
| Package | Affected | Fixed in |
|---|---|---|
coa npm | All versions | None |
coa npm | All versions | None |
How do I fix GHSA-73qr-pfmq-6rp8?
No fix has been published for GHSA-73qr-pfmq-6rp8 yet. Limit exposure of the affected software until one is available.
Is GHSA-73qr-pfmq-6rp8 being exploited?
There is no known exploitation of GHSA-73qr-pfmq-6rp8 in the wild and no public exploit code.