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

> Remote attackers can list files hosted by the web application due to a site-wide directory listing vulnerability in actiNAS devices.

- **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:** 19 Jan 2024
- **Updated:** 20 Jun 2025
- **Also known as:** GHSA-99vg-whp9-cxq4

## What is CVE-2023-51948?

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

### Official description

A Site-wide directory listing vulnerability in /fm in actidata actiNAS SL 2U-8 RDX 3.2.03-SP1 allows remote attackers to list the files hosted by the web application.

Weakness: CWE-548 (Exposure of Information Through Directory Listing)

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

It affects 1 product.


Products: Actidata Actinas Sl 2u-8 Rdx Firmware.

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

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

## Is CVE-2023-51948 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-51947](https://insights.sbomify.com/CVE-2023-51947/): Missing authorization in n/a (critical 9.1)
- [CVE-2023-51946](https://insights.sbomify.com/CVE-2023-51946/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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