# CVE-2024-31977: Command injection in n/a

> Attackers can execute arbitrary OS commands via shell metacharacters in Ping or Traceroute utilities on Adtran devices.

- **Severity:** High 8.0 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 24 Jul 2024
- **Updated:** 4 Sep 2024
- **Also known as:** GHSA-4r38-rqh5-3fvr

## What is CVE-2024-31977?

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

### Official description

Adtran 834-5 11.1.0.101-202106231430, and fixed as of SmartOS Version 12.6.3.1, devices allow OS Command Injection via shell metacharacters to the Ping or Traceroute utility.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2024-31977?

It affects 2 products.


Products: Adtran 834-5 Firmware, Adtran Sdg Smartos.

## How do I fix CVE-2024-31977?

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

## Is CVE-2024-31977 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-31977 and fix it if it is affected.

What it is: CVE-2024-31977 is a high-severity command injection vulnerability in n/a, published on 24 Jul 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-2024-31977 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-2024-31977/ (Markdown: https://insights.sbomify.com/CVE-2024-31977/index.md)
```

## Sources

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

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