# CVE-2025-3659: Improper authentication handling for Digi PortServer TS; Digi One SP, SP IA, IA; Digi One IAP

> Unauthenticated attackers can modify configuration settings via crafted HTTP POST requests to Digi serial device web interfaces.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 May 2025
- **Updated:** 12 May 2025
- **Also known as:** GHSA-r6rh-c775-h225

## What is CVE-2025-3659?

CVE-2025-3659 is a critical authentication bypass vulnerability in Digi One IAP, published on 12 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper authentication handling was identified in a set of HTTP POST requests affecting the following product families: 

  *  Digi PortServer TS - prior to and including 82000747_AA, build date 06/17/2022

  *  Digi One SP/Digi One SP IA/Digi One IA - prior to and including 82000774_Z, build date 10/19/2020

  *  Digi One IAP – prior to and including 82000770 Z, build date 10/19/2020

A specially crafted POST request to the device’s web interface may allow an unauthenticated attacker to modify configuration settings.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2025-3659?


## How do I fix CVE-2025-3659?

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

## Is CVE-2025-3659 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3659 and fix it if it is affected.

What it is: CVE-2025-3659 is a critical authentication bypass vulnerability in Digi One IAP, published on 12 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-3659 in the wild and no public exploit code.

Affected product: Digi One IAP. 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-2025-3659/ (Markdown: https://insights.sbomify.com/CVE-2025-3659/index.md)
```

## Sources

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

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