# CVE-2018-0688: Open redirect in SEIKO EPSON printers and scanners > Attackers can redirect users to malicious sites via vulnerable Epson printer and scanner firmware interfaces. - **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`) - **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:** 9 Jan 2019 - **Updated:** 5 Aug 2024 - **Also known as:** GHSA-qf5r-mp49-68fr ## What is CVE-2018-0688? CVE-2018-0688 is a medium-severity vulnerability in SEIKO EPSON printers and scanners, published on 9 Jan 2019. 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 Open redirect vulnerability in SEIKO EPSON printers and scanners (DS-570W firmware versions released prior to 2018 March 13, DS-780N firmware versions released prior to 2018 March 13, EP-10VA firmware versions released prior to 2017 September 4, EP-30VA firmware versions released prior to 2017 June 19, EP-707A firmware versions released prior to 2017 August 1, EP-708A firmware versions released prior to 2017 August 7, EP-709A firmware versions released prior to 2017 June 12, EP-777A firmware versions released prior to 2017 August 1, EP-807AB/AW/AR firmware versions released prior to 2017 August 1, EP-808AB/AW/AR firmware versions released prior to 2017 August 7, EP-879AB/AW/AR firmware versions released prior to 2017 June 12, EP-907F firmware versions released prior to 2017 August 1, EP-977A3 firmware versions released prior to 2017 August 1, EP-978A3 firmware versions released prior to 2017 August 7, EP-979A3 firmware versions released prior to 2017 June 12, EP-M570T firmware versions released prior to 2017 September 6, EW-M5071FT firmware versions released prior to 2017 November 2, EW-M660FT firmware versions released prior to 2018 April 19, EW-M770T firmware versions released prior to 2017 September 6, PF-70 firmware versions released prior to 2018 April 20, PF-71 firmware versions released prior to 2017 July 18, PF-81 firmware versions released prior to 2017 September 14, PX-048A firmware versions released prior to 2017 July 4, PX-049A firmware versions released prior to 2017 September 11, PX-437A firmware versions released prior to 2017 July 24, PX-M350F firmware versions released prior to 2018 February 23, PX-M5040F firmware versions released prior to 2017 November 20, PX-M5041F firmware versions released prior to 2017 November 20, PX-M650A firmware versions released prior to 2017 October 17, PX-M650F firmware versions released prior to 2017 October 17, PX-M680F firmware versions released prior to 2017 June 29, PX-M7050F firmware versions released prior to 2017 October 13, PX-M7050FP firmware versions released prior to 2017 October 13, PX-M7050FX firmware versions released prior to 2017 November 7, PX-M7070FX firmware versions released prior to 2017 April 27, PX-M740F firmware versions released prior to 2017 December 4, PX-M741F firmware versions released prior to 2017 December 4, PX-M780F firmware versions released prior to 2017 June 29, PX-M781F firmware versions released prior to 2017 June 27, PX-M840F firmware versions released prior to 2017 November 16, PX-M840FX firmware versions released prior to 2017 December 8, PX-M860F firmware versions released prior to 2017 October 25, PX-S05B/W firmware versions released prior to 2018 March 9, PX-S350 firmware versions released prior to 2018 February 23, PX-S5040 firmware versions released prior to 2017 November 20, PX-S7050 firmware versions released prior to 2018 February 21, PX-S7050PS firmware versions released prior to 2018 February 21, PX-S7050X firmware versions released prior to 2017 November 7, PX-S7070X firmware versions released prior to 2017 April 27, PX-S740 firmware versions released prior to 2017 December 3, PX-S840 firmware versions released prior to 2017 November 16, PX-S840X firmware versions released prior to 2017 December 8, PX-S860 firmware versions released prior to 2017 December 7) allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via the web interface of the affected product. Weakness: CWE-601 (URL Redirection to Untrusted Site) ## Which versions are affected by CVE-2018-0688? It affects 58 products. Products: Epson Ds-570w Firmware, Epson Ds-780n Firmware, Epson Ep-10va Firmware, Epson Ep-30va Firmware, Epson Ep-707a Firmware, Epson Ep-708a Firmware, Epson Ep-709a Firmware, Epson Ep-777a Firmware, Epson Ep-807ab Firmware, Epson Ep-807ar Firmware, Epson Ep-807aw Firmware, Epson Ep-808ab Firmware, Epson Ep-808ar Firmware, Epson Ep-808aw Firmware, Epson Ep-879ab Firmware, Epson Ep-879ar Firmware, Epson Ep-879aw Firmware, Epson Ep-907f Firmware, Epson Ep-977a3 Firmware, Epson Ep-978a3 Firmware and 38 more. ## How do I fix CVE-2018-0688? No fix has been published for CVE-2018-0688 yet. Limit exposure of the affected software until one is available. ## Is CVE-2018-0688 being exploited? There is no known exploitation of CVE-2018-0688 in the wild and no public exploit code. ## Other vulnerabilities in SEIKO EPSON printers and scanners - [CVE-2018-0689](https://insights.sbomify.com/CVE-2018-0689/): Other in SEIKO EPSON printers and scanners (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2018-0688 and fix it if it is affected. What it is: CVE-2018-0688 is a medium-severity vulnerability in SEIKO EPSON printers and scanners, published on 9 Jan 2019. 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-2018-0688 in the wild and no public exploit code. Affected product: SEIKO EPSON printers and scanners. 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-0688/ (Markdown: https://insights.sbomify.com/CVE-2018-0688/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2018-0688 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-0688 - OSV: https://osv.dev/vulnerability/CVE-2018-0688 --- From sbomify Insights: https://insights.sbomify.com/CVE-2018-0688/ Summaries are generated and may contain mistakes; the official description above is the record.