# CVE-2018-7236: Auth bypass in Pelco Sarix Professional

> An authentication bypass in the set_param endpoint allows attackers to enable SSH service, potentially leading to unauthorized access and code execution on Pelco cameras.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Mar 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-9rxc-jvqg-fv36

## What is CVE-2018-7236?

CVE-2018-7236 is a high-severity authentication bypass vulnerability in Schneider Electric SE Pelco Sarix Professional, published on 9 Mar 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability exists in Schneider Electric's Pelco Sarix Professional in all firmware versions prior to 3.29.67 which could enable SSH service due to lack of authentication for /login/bin/set_param could enable SSH service.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2018-7236?

It affects 20 products.


Products: Schneider-Electric Ibp1110-1er Firmware, Schneider-Electric Ibp219-1er Firmware, Schneider-Electric Ibp319-1er Firmware, Schneider-Electric Ibp519-1er Firmware, Schneider-Electric Ibps110-1er Firmware, Schneider-Electric Imp1110-1 Firmware, Schneider-Electric Imp1110-1e Firmware, Schneider-Electric Imp1110-1er Firmware, Schneider-Electric Imp219-1 Firmware, Schneider-Electric Imp219-1e Firmware, Schneider-Electric Imp219-1er Firmware, Schneider-Electric Imp319-1 Firmware, Schneider-Electric Imp319-1e Firmware, Schneider-Electric Imp319-1er Firmware, Schneider-Electric Imp519-1 Firmware, Schneider-Electric Imp519-1e Firmware, Schneider-Electric Imp519-1er Firmware, Schneider-Electric Imps110-1e Firmware, Schneider-Electric Imps110-1er Firmware, Schneider-Electric Mps110-1 Firmware.

## How do I fix CVE-2018-7236?

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

## Is CVE-2018-7236 being exploited?

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

## Other vulnerabilities in Schneider Electric SE Pelco Sarix Professional

- [CVE-2018-7780](https://insights.sbomify.com/CVE-2018-7780/): Memory corruption in Pelco Sarix Professional V1 (critical 9.8)
- [CVE-2018-7228](https://insights.sbomify.com/CVE-2018-7228/): Auth bypass in Pelco Sarix Professional (critical 9.8)
- [CVE-2018-7229](https://insights.sbomify.com/CVE-2018-7229/): Hardcoded credentials in Pelco Sarix Professional (critical 9.8)
- [CVE-2018-7231](https://insights.sbomify.com/CVE-2018-7231/): Command injection in Pelco Sarix Professional (critical 9.8)
- [CVE-2018-7232](https://insights.sbomify.com/CVE-2018-7232/): Command injection in Pelco Sarix Professional (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-7236 and fix it if it is affected.

What it is: CVE-2018-7236 is a high-severity authentication bypass vulnerability in Schneider Electric SE Pelco Sarix Professional, published on 9 Mar 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-7236 in the wild and no public exploit code.

Affected product: Schneider Electric SE Pelco Sarix Professional. 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-2018-7236/ (Markdown: https://insights.sbomify.com/CVE-2018-7236/index.md)
```

## Sources

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

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