# CVE-2022-27632: Cross-site request forgery in Rebooter, PoE Rebooter, Scheduler, and Contact Converter

> Remote attackers can hijack administrator sessions and perform arbitrary operations via CSRF in MEIKYO ELECTRIC rebooters and schedulers.

- **Severity:** High 8.8 (`CVSS:3.1/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:** 18 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-qgj5-3w7x-wf28

## What is CVE-2022-27632?

CVE-2022-27632 is a high-severity vulnerability in MEIKYO ELECTRIC CO.,LTD. Rebooter, PoE Rebooter, Scheduler, and Contact Converter, published on 18 May 2022. 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

Cross-site request forgery (CSRF) vulnerability in Rebooter(WATCH BOOT nino RPC-M2C [End of Sale] all firmware versions, WATCH BOOT light RPC-M5C [End of Sale] all firmware versions, WATCH BOOT L-zero RPC-M4L [End of Sale] all firmware versions, WATCH BOOT mini RPC-M4H [End of Sale] all firmware versions, WATCH BOOT nino RPC-M2CS firmware version 1.00A to 1.00D, WATCH BOOT light RPC-M5CS firmware version 1.00A to 1.00D, WATCH BOOT L-zero RPC-M4LS firmware version 1.00A to 1.20A, and Signage Rebooter RPC-M4HSi firmware version 1.00A), PoE Rebooter(PoE BOOT nino PoE8M2 firmware version 1.00A to 1.20A), Scheduler(TIME BOOT mini RSC-MT4H [End of Sale] all firmware versions, TIME BOOT RSC-MT8F [End of Sale] all firmware versions, TIME BOOT RSC-MT8FP [End of Sale] all firmware versions, TIME BOOT mini RSC-MT4HS firmware version 1.00A to 1.10A, and TIME BOOT RSC-MT8FS firmware version 1.00A to 1.00E), and Contact Converter(POSE SE10-8A7B1 firmware version 1.00A to 1.20A) allows a remote attacker to hijack the authentication of an administrator and conduct arbitrary operations by having a user to view a specially crafted page.

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

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

It affects 15 products.


Products: Meikyo Poe Boot Nino Poe8m2 Firmware, Meikyo Pose Se10-8a7b1 Firmware, Meikyo Signage Rebooter Rpc-M4hsi Firmware, Meikyo Time Boot Mini Rsc-Mt4h Firmware, Meikyo Time Boot Mini Rsc-Mt4hs Firmware, Meikyo Time Boot Rsc-Mt8f Firmware, Meikyo Time Boot Rsc-Mt8fp Firmware, Meikyo Time Boot Rsc-Mt8fs Firmware, Meikyo Watch Boot L-Zero Rpc-M4l Firmware, Meikyo Watch Boot L-Zero Rpc-M4ls Firmware, Meikyo Watch Boot Light Rpc-M5c Firmware, Meikyo Watch Boot Light Rpc-M5cs Firmware, Meikyo Watch Boot Mini Rpc-M4h Firmware, Meikyo Watch Boot Nino Rpc-M2c Firmware, Meikyo Watch Boot Nino Rpc-M2cs Firmware.

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

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

## Is CVE-2022-27632 being exploited?

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

## Other vulnerabilities in MEIKYO ELECTRIC CO.,LTD. Rebooter, PoE Rebooter, Scheduler, and Contact Converter

- [CVE-2022-28717](https://insights.sbomify.com/CVE-2022-28717/): Cross-site scripting in Rebooter, PoE Rebooter, Scheduler, and Contact Converter (medium 4.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-27632 is a high-severity vulnerability in MEIKYO ELECTRIC CO.,LTD. Rebooter, PoE Rebooter, Scheduler, and Contact Converter, published on 18 May 2022. 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-2022-27632 in the wild and no public exploit code.

Affected product: MEIKYO ELECTRIC CO.,LTD. Rebooter, PoE Rebooter, Scheduler, and Contact Converter. 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-27632/ (Markdown: https://insights.sbomify.com/CVE-2022-27632/index.md)
```

## Sources

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

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