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

> Remote attackers can modify arbitrary user passwords in PivotX, leading to account takeover without authentication.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/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:** 18 Feb 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mfx4-mv99-gv77

## What is CVE-2011-1035?

CVE-2011-1035 is a high-severity authentication bypass vulnerability in n/a, published on 18 Feb 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The password reset in PivotX before 2.2.4 allows remote attackers to modify the passwords of arbitrary users via unspecified vectors.

Weakness: CWE-255

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

It affects 1 product.


Products: Pivotx Pivotx.

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

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

## Is CVE-2011-1035 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-8402](https://insights.sbomify.com/CVE-2017-8402/): File upload in n/a (high 8.8)
- [CVE-2017-7570](https://insights.sbomify.com/CVE-2017-7570/): File upload in n/a (high 8.8)
- [CVE-2015-5457](https://insights.sbomify.com/CVE-2015-5457/): File upload in n/a (high 7.5)
- [CVE-2014-0342](https://insights.sbomify.com/CVE-2014-0342/): File upload in n/a (high 7.5)
- [CVE-2017-14958](https://insights.sbomify.com/CVE-2017-14958/): File upload in n/a (high 7.2)

## Fix prompt for AI coding agents

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

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

## Sources

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

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