# CVE-2022-2661: Sequi PortBloque S Improper Authorization

> A low-privileged user can perform administrative functions on Sequi PortBloque S devices via crafted requests, requiring vendor patches.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Aug 2022
- **Updated:** 16 Apr 2025
- **Also known as:** GHSA-jpf9-qwfv-jpp5

## What is CVE-2022-2661?

CVE-2022-2661 is a critical missing authorization vulnerability in Sequi PortBloque S, published on 16 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Sequi PortBloque S has an improper authorization vulnerability, which may allow a low-privileged user to perform administrative functions using specifically crafted requests.

Weakness: CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2022-2661?

It affects 1 product.


Products: Sequi Portbloque S Firmware.

## How do I fix CVE-2022-2661?

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

## Is CVE-2022-2661 being exploited?

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

## Other vulnerabilities in Sequi PortBloque S

- [CVE-2022-2662](https://insights.sbomify.com/CVE-2022-2662/): Sequi PortBloque S Improper Authentication (critical 9.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-2661 and fix it if it is affected.

What it is: CVE-2022-2661 is a critical missing authorization vulnerability in Sequi PortBloque S, published on 16 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-2661 in the wild and no public exploit code.

Affected product: Sequi PortBloque S. 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-2022-2661/ (Markdown: https://insights.sbomify.com/CVE-2022-2661/index.md)
```

## Sources

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

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