CVE-2019-10802 OS Command Injection in giting
Critical 9.8
Published
Updated
Check this codebase for CVE-2019-10802 and fix it if it is affected.
What it is: CVE-2019-10802 is a critical vulnerability in giting, published on 28 Feb 2020.
Exploitation: There is no known exploitation of CVE-2019-10802 in the wild and no public exploit code.
Affected packages and fixed versions:
- giting (npm): affected all versions up to 0.0.8; no fix listed
- giting (npm): affected all versions up to 0.0.8; 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/CVE-2019-10802/ (Markdown: https://insights.sbomify.com/CVE-2019-10802/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2019-10802?
CVE-2019-10802 is a critical vulnerability in giting, published on 28 Feb 2020.
Official description
giting version prior to 0.0.8 allows execution of arbritary commands. The first argument "repo" of function "pull()" is executed by the package without any validation.
Weakness: CWE-78
Which versions are affected by CVE-2019-10802?
2 open source packages ship an affected version, including giting. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
giting npm | All versions to 0.0.8 | None |
giting npm | All versions to 0.0.8 | None |
Products include Mangoraft Giting.
How do I fix CVE-2019-10802?
No fix has been published for CVE-2019-10802 yet. Limit exposure of the affected software until one is available.
Is CVE-2019-10802 being exploited?
There is no known exploitation of CVE-2019-10802 in the wild and no public exploit code.
Sources
Also known as GHSA-53xj-v576-3ch2.