How severe is GHSA-cr67-78jr-j94p?

No CVSS score has been assigned to GHSA-cr67-78jr-j94p yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-cr67-78jr-j94p?

GHSA-cr67-78jr-j94p affects the following packages: domokeeper (npm). Ecosystems affected: npm.

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

No patched version of domokeeper has shipped for GHSA-cr67-78jr-j94p yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-cr67-78jr-j94p in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for domokeeper, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-cr67-78jr-j94p if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-cr67-78jr-j94p actively exploited in the wild?

No public exploit code has been indexed for GHSA-cr67-78jr-j94p yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-cr67-78jr-j94p published, and has it been updated?

GHSA-cr67-78jr-j94p was published on September 3, 2020 and was last updated on August 31, 2020. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Local File Inclusion in domokeeperGHSA-cr67-78jr-j94p

GHSA-cr67-78jr-j94p is a security vulnerability in domokeeper. No vendor fix is recorded yet; mitigation options are listed below.

Published

Sep 3, 2020

Updated

Aug 31, 2020

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

domokeepernpm

1downloads / week

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.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`domokeeper`	≥ 0.0.0	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for domokeeper, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of domokeeper has shipped for GHSA-cr67-78jr-j94p yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-cr67-78jr-j94p in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works