# CVE-2024-22438: HPE OfficeConnect 1820 Network switches, Cross-Site Request Forgery (CSRF)

> Remote attackers can exploit CSRF to execute malicious code on HPE OfficeConnect 1820 network switches.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Apr 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-5vxm-h3q8-5xvm

## What is CVE-2024-22438?

CVE-2024-22438 is a low-severity vulnerability in Hewlett Packard Enterprise HPE OfficeConnect 1820 Network switches, published on 15 Apr 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

A potential security vulnerability has been identified in Hewlett Packard Enterprise OfficeConnect 1820 Network switches. The vulnerability could be remotely exploited to allow execution of malicious code.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2024-22438?


## How do I fix CVE-2024-22438?

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

## Is CVE-2024-22438 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-22438 and fix it if it is affected.

What it is: CVE-2024-22438 is a low-severity vulnerability in Hewlett Packard Enterprise HPE OfficeConnect 1820 Network switches, published on 15 Apr 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-22438 in the wild and no public exploit code.

Affected product: Hewlett Packard Enterprise HPE OfficeConnect 1820 Network switches. 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-2024-22438/ (Markdown: https://insights.sbomify.com/CVE-2024-22438/index.md)
```

## Sources

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

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