# CVE-2020-29311: Command injection in n/a

> Attackers can execute arbitrary commands as root by injecting malicious code into the configuration file, leading to full system compromise.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-473q-vgvv-5537

## What is CVE-2020-29311?

CVE-2020-29311 is a critical command injection vulnerability in n/a, published on 10 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Ubilling v1.0.9 allows Remote Command Execution as Root user by executing a malicious command that is injected inside the config file and being triggered by another part of the software.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2020-29311?

It affects 1 product.


Products: Ubilling Ubilling.

## How do I fix CVE-2020-29311?

No fix has been published for CVE-2020-29311 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-29311 being exploited?

There is no known exploitation of CVE-2020-29311 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2018-1000827](https://insights.sbomify.com/CVE-2018-1000827/): Deserialization in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-29311 and fix it if it is affected.

What it is: CVE-2020-29311 is a critical command injection vulnerability in n/a, published on 10 Dec 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 CVE-2020-29311 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2020-29311/ (Markdown: https://insights.sbomify.com/CVE-2020-29311/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-29311
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-29311
- OSV: https://osv.dev/vulnerability/CVE-2020-29311

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-29311/
Summaries are generated and may contain mistakes; the official description above is the record.