# CVE-2013-4097: Information disclosure in n/a

> Remote attackers can obtain sensitive installation path information by directly requesting a specific JSP file in DS3 Authentication Server.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/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:** 28 Jun 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-xxhr-wjq6-3g79

## What is CVE-2013-4097?

CVE-2013-4097 is a medium-severity vulnerability in n/a, published on 28 Jun 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ServerAdmin/TestDRConnection.jsp in DS3 Authentication Server allows remote attackers to obtain sensitive information via a direct request, which reveals the installation path in a -REG-E-OPEN error message.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2013-4097?

It affects 1 product.


Products: Ds3 Authentication Server.

## How do I fix CVE-2013-4097?

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

## Is CVE-2013-4097 being exploited?

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

Public exploit code:

- DS3 Authentication Server - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2013-4096](https://insights.sbomify.com/CVE-2013-4096/): Command injection in n/a (critical 9.0)
- [CVE-2013-4098](https://insights.sbomify.com/CVE-2013-4098/): Cross-site scripting in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-4097 and fix it if it is affected.

What it is: CVE-2013-4097 is a medium-severity vulnerability in n/a, published on 28 Jun 2013. 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-2013-4097 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-2013-4097/ (Markdown: https://insights.sbomify.com/CVE-2013-4097/index.md)
```

## Sources

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

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