# GHSA-mgv2-57vj-99xc: Low severity vulnerability that affects eye.js


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 7 Oct 2019

## What is GHSA-mgv2-57vj-99xc?

GHSA-mgv2-57vj-99xc is a vulnerability in eye.js, published on 7 Oct 2019. 

### Official description

## Test breaking

### Impact
In v1.2.0, tests are broken: all tests are always succeeding. If tests are looking for security vulnerabilities, these were compromised.

### Patches
Users should upgrade to `v1.2.1`

### Workarounds
Users who don't use eye.js for looking for vulnerabilities are safe. Upgrading will just fix some bugs.

### For more information
If you have any questions or comments about this advisory:
* Open an issue in [EyeJS](https://github.com/arguiot/EyeJS)
* Email us at [arguiot@gmail.com](mailto:arguiot@gmail.com)

## Which versions are affected by GHSA-mgv2-57vj-99xc?

2 open source packages ship an affected version, including eye.js.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `eye.js` | npm | From 1.2.0 | 1.2.1 |
| `eye.js` | npm | From 1.2.0 | 1.2.1 |

## How do I fix GHSA-mgv2-57vj-99xc?

Upgrade eye.js to 1.2.1 or later.

## Is GHSA-mgv2-57vj-99xc being exploited?

There is no known exploitation of GHSA-mgv2-57vj-99xc in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-mgv2-57vj-99xc and fix it if it is affected.

What it is: GHSA-mgv2-57vj-99xc is a vulnerability in eye.js, published on 7 Oct 2019. 
Exploitation: There is no known exploitation of GHSA-mgv2-57vj-99xc in the wild and no public exploit code.

Affected packages and fixed versions:
- eye.js (npm): affected from 1.2.0; fixed in 1.2.1
- eye.js (npm): affected from 1.2.0; fixed in 1.2.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-mgv2-57vj-99xc/ (Markdown: https://insights.sbomify.com/GHSA-mgv2-57vj-99xc/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-mgv2-57vj-99xc

---
From sbomify Insights: https://insights.sbomify.com/GHSA-mgv2-57vj-99xc/
Summaries are generated and may contain mistakes; the official description above is the record.