# CVE-2011-1858: Auth bypass in n/a

> Local attackers can bypass access restrictions in HP Service Manager and Service Center to gain unauthorized privileges.

- **Severity:** Medium 4.3 (`AV:L/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jun 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-j2v7-mg5j-hjc3

## What is CVE-2011-1858?

CVE-2011-1858 is a medium-severity authentication bypass vulnerability in n/a, published on 14 Jun 2011. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unspecified vulnerability in HP Service Manager 7.02, 7.11, 9.20, and 9.21 and Service Center 6.2.8 allows local users to bypass intended access restrictions via unknown vectors.

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

It affects 2 products.


Products: Hp Service Center, Hp Service Manager.

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

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

## Is CVE-2011-1858 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-4808](https://insights.sbomify.com/CVE-2013-4808/): Auth bypass in n/a (critical 10.0)
- [CVE-2011-1861](https://insights.sbomify.com/CVE-2011-1861/): Information disclosure in n/a (high 8.3)
- [CVE-2011-1857](https://insights.sbomify.com/CVE-2011-1857/): Auth bypass in n/a (high 8.2)
- [CVE-2013-4844](https://insights.sbomify.com/CVE-2013-4844/): Code injection in n/a (high 7.5)
- [CVE-2012-5214](https://insights.sbomify.com/CVE-2012-5214/): Other in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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