# CVE-2023-44037: Information disclosure in n/a

> A remote attacker can obtain sensitive information from the TACACS+ server component in Nodegrid OS.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2023
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-hcph-762f-fp48

## What is CVE-2023-44037?

CVE-2023-44037 is a high-severity vulnerability in n/a, published on 14 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in ZPE Systems, Inc Nodegrid OS v.5.8.10 thru v.5.8.13 and v.5.10.3 thru v.5.10.5 allows a remote attacker to obtain sensitive information via the TACACS+ server component.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2023-44037?

It affects 1 product.


Products: Zpesystems Nodegrid Os.

## How do I fix CVE-2023-44037?

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

## Is CVE-2023-44037 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-43322](https://insights.sbomify.com/CVE-2023-43322/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-44037 and fix it if it is affected.

What it is: CVE-2023-44037 is a high-severity vulnerability in n/a, published on 14 Oct 2023. 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-2023-44037 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-2023-44037/ (Markdown: https://insights.sbomify.com/CVE-2023-44037/index.md)
```

## Sources

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

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