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

> Remote attackers can obtain sensitive information from HP IceWall SSO products via unspecified vectors.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 23 Sep 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-x8gq-747j-wchg

## What is CVE-2013-4818?

CVE-2013-4818 is a medium-severity vulnerability in n/a, published on 23 Sep 2013. It can be exploited over the network.

### Official description

Unspecified vulnerability in HP IceWall SSO 8.0 through 10.0, IceWall SSO Agent Option 8.0 through 10.0, IceWall SSO Smart Device Option 10.0, and IceWall File Manager 3.0 through SP4 allows remote attackers to obtain sensitive information via unknown vectors.

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

It affects 4 products.


Products: Hp Icewall File Manager, Hp Icewall Smart Device Option, Hp Icewall Sso Agent, Hp Icewall Sso Agent Option.

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

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

## Is CVE-2013-4818 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-4818 is a medium-severity vulnerability in n/a, published on 23 Sep 2013. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2013-4818 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-4818/ (Markdown: https://insights.sbomify.com/CVE-2013-4818/index.md)
```

## Sources

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

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