# CVE-2011-1514: Null dereference in n/a

> Remote attackers can crash the HP OpenView Storage Data Protector inet service via crafted requests, causing denial of service.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jul 2011
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-jr8v-8qcf-fp2p

## What is CVE-2011-1514?

CVE-2011-1514 is a medium-severity vulnerability in n/a, published on 1 Jul 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The inet service in HP OpenView Storage Data Protector 6.00 through 6.20 allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via a request containing crafted parameters.

## Which versions are affected by CVE-2011-1514?

It affects 1 product.


Products: Hp Openview Storage Data Protector.

## How do I fix CVE-2011-1514?

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

## Is CVE-2011-1514 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-1865](https://insights.sbomify.com/CVE-2011-1865/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-1866](https://insights.sbomify.com/CVE-2011-1866/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-1728](https://insights.sbomify.com/CVE-2011-1728/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-1729](https://insights.sbomify.com/CVE-2011-1729/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-1730](https://insights.sbomify.com/CVE-2011-1730/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-1514 and fix it if it is affected.

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

## Sources

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

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