# GHSA-cr67-78jr-j94p: Local File Inclusion in domokeeper

> Attackers can exploit unsanitized input in the domokeeper package to execute arbitrary code or read sensitive JSON files via local file inclusion.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Sep 2020

## What is GHSA-cr67-78jr-j94p?

GHSA-cr67-78jr-j94p is a path traversal vulnerability in domokeeper, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

All versions of `domokeeper` are vulnerable to Local File Inclusion. The `/plugin/` route passes a GET parameter unsanitized to a `require()` call. It then returns the output of `require()` in the server response. This may allow attackers to load unintended code in the application. It also allows attackers to exfiltrate information in `.json` files.

## Recommendation

No fix is currently available. Consider using an alternative package until a fix is made available.

## Which versions are affected by GHSA-cr67-78jr-j94p?

2 open source packages ship an affected version, including domokeeper.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `domokeeper` | npm | From 0.0.0 | None |
| `domokeeper` | npm | From 0.0.0 | None |

## How do I fix GHSA-cr67-78jr-j94p?

No fix has been published for GHSA-cr67-78jr-j94p yet. Limit exposure of the affected software until one is available.

## Is GHSA-cr67-78jr-j94p being exploited?

There is no known exploitation of GHSA-cr67-78jr-j94p in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-cr67-78jr-j94p and fix it if it is affected.

What it is: GHSA-cr67-78jr-j94p is a path traversal vulnerability in domokeeper, published on 3 Sep 2020. 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-cr67-78jr-j94p in the wild and no public exploit code.

Affected packages and fixed versions:
- domokeeper (npm): affected from 0.0.0; no fix listed
- domokeeper (npm): affected from 0.0.0; 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-cr67-78jr-j94p/ (Markdown: https://insights.sbomify.com/GHSA-cr67-78jr-j94p/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-cr67-78jr-j94p

---
From sbomify Insights: https://insights.sbomify.com/GHSA-cr67-78jr-j94p/
Summaries are generated and may contain mistakes; the official description above is the record.