# CVE-2018-7055: Server-side request forgery in n/a

> An attacker can exploit a Server-Side Request Forgery vulnerability in RoomWizard to access internal resources via the url parameter.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rg43-2qfx-hv4g

## What is CVE-2018-7055?

CVE-2018-7055 is a high-severity server-side request forgery vulnerability in n/a, published on 15 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

GroupViewProxyServlet in RoomWizard before 4.4.x allows SSRF via the url parameter.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Steelcase Roomwizard Firmware.

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

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

## Is CVE-2018-7055 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-7057](https://insights.sbomify.com/CVE-2018-7057/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2018-7056](https://insights.sbomify.com/CVE-2018-7056/): RoomWizard before 4.4.x allows remote attackers to obtain potentially sensitive information about IP addresses via /getGroupTimeLineJSON.action. (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-7055 is a high-severity server-side request forgery vulnerability in n/a, published on 15 Feb 2018. 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-2018-7055 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-2018-7055/ (Markdown: https://insights.sbomify.com/CVE-2018-7055/index.md)
```

## Sources

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

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