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

> Physically proximate attackers can view sensitive administrative information on unattended workstations because the browser fails to close pages upon session timeout.

- **Severity:** Low 1.9 (`AV:L/AC:M/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jun 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-v5w6-658c-5g4v

## What is CVE-2013-0527?

CVE-2013-0527 is a low-severity vulnerability in n/a, published on 21 Jun 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Browser in IBM Sterling Connect:Direct 1.4 before 1.4.0.11 and 1.5 through 1.5.0.1 does not close pages upon the timeout of a session, which allows physically proximate attackers to obtain sensitive administrative-console information by reading the screen of an unattended workstation.

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

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

It affects 1 product.


Products: Ibm Sterling Connect Direct User Interface.

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

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

## Is CVE-2013-0527 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-20560](https://insights.sbomify.com/CVE-2021-20560/): Other in Sterling Connect:Direct Browser User Interface (medium 5.4)
- [CVE-2013-0529](https://insights.sbomify.com/CVE-2013-0529/): Security feature bypass in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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