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

> Remote attackers can access sensitive configuration data by directly requesting a specific HTML file due to missing exit after redirect.

- **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:** 14 Feb 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-xwfq-89j4-72rw

## What is CVE-2013-1402?

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

### Official description

DigiLIBE 3.4 and possibly other versions sends a redirect but does not exit, which allows remote attackers to obtain sensitive configuration information via a direct request to configuration/general_configuration.html.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Digitiliti Digilibe.

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

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

## Is CVE-2013-1402 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-1402 exists.

Public exploit code:

- DigiLIBE - Execution-After-Redirect Information Disclosure (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-1402 is a medium-severity vulnerability in n/a, published on 14 Feb 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-1402 exists.

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-1402/ (Markdown: https://insights.sbomify.com/CVE-2013-1402/index.md)
```

## Sources

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

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