# CVE-2021-27702: Command injection in n/a

> Attackers can execute arbitrary commands via the diagnostic utility in the Sercomm Etisalat S3-AC2100 router dashboard.

- **Severity:** High 7.3 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Nov 2024
- **Updated:** 15 Nov 2024
- **Also known as:** GHSA-72v3-rgjm-mj6f

## What is CVE-2021-27702?

CVE-2021-27702 is a high-severity command injection vulnerability in n/a, published on 12 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Sercomm Router Etisalat Model S3- AC2100 is affected by Incorrect Access Control via the diagnostic utility in the router dashboard.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2021-27702?


## How do I fix CVE-2021-27702?

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

## Is CVE-2021-27702 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-27702 and fix it if it is affected.

What it is: CVE-2021-27702 is a high-severity command injection vulnerability in n/a, published on 12 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-27702 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-2021-27702/ (Markdown: https://insights.sbomify.com/CVE-2021-27702/index.md)
```

## Sources

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

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