# CVE-2018-17903: Other in SAGA1-L8B

> Attackers can perform replay attacks and forge commands on SAGA1-L8B devices, compromising industrial control operations.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Oct 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-rjm3-978x-473m

## What is CVE-2018-17903?

CVE-2018-17903 is a critical vulnerability in GAIN Electronic Co. Ltd SAGA1-L8B, published on 24 Oct 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SAGA1-L8B with any firmware versions prior to A0.10 are vulnerable to a replay attack and command forgery.

Weakness: CWE-294 (Authentication Bypass by Capture-replay)

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

It affects 1 product.


Products: Sagaradio Saga1-L8b Firmware.

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

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

## Is CVE-2018-17903 being exploited?

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

## Other vulnerabilities in GAIN Electronic Co. Ltd SAGA1-L8B

- [CVE-2018-17921](https://insights.sbomify.com/CVE-2018-17921/): Auth bypass in SAGA1-L8B (high 8.8)
- [CVE-2018-17923](https://insights.sbomify.com/CVE-2018-17923/): Auth bypass in SAGA1-L8B (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-17903 is a critical vulnerability in GAIN Electronic Co. Ltd SAGA1-L8B, published on 24 Oct 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-17903 in the wild and no public exploit code.

Affected product: GAIN Electronic Co. Ltd SAGA1-L8B. 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-17903/ (Markdown: https://insights.sbomify.com/CVE-2018-17903/index.md)
```

## Sources

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

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