# CVE-2017-5796: Cross-site request forgery in 2620 Series Network Switches

> Attackers can perform unauthorized actions on HPE 2620 switches via CSRF, requiring administrative attention to patch.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 15 Feb 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-98qm-prfj-4q3r

## What is CVE-2017-5796?

CVE-2017-5796 is a high-severity vulnerability in Hewlett Packard Enterprise 2620 Series Network Switches, published on 15 Feb 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 Remote Cross Site Request Forgery (CSRF) vulnerability in HPE 2620 Series Network Switches version RA.15.05.0006 was found.

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

## Which versions are affected by CVE-2017-5796?

It affects 5 products.


Products: Hp J9623a Firmware, Hp J9624a Firmware, Hp J9625a Firmware, Hp J9626a Firmware, Hp J9627a Firmware.

## How do I fix CVE-2017-5796?

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

## Is CVE-2017-5796 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-5796 and fix it if it is affected.

What it is: CVE-2017-5796 is a high-severity vulnerability in Hewlett Packard Enterprise 2620 Series Network Switches, published on 15 Feb 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-2017-5796 in the wild and no public exploit code.

Affected product: Hewlett Packard Enterprise 2620 Series 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-2017-5796/ (Markdown: https://insights.sbomify.com/CVE-2017-5796/index.md)
```

## Sources

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

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