Read the docs

User-controlled Duo host enables SSRF in Psono Server

Priority LOW 24CWE-918Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
Low · None · Low
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA.

Summary

Psono Server CE and EE from 0.1.0 before 7.2.4 accept a user-controlled host when configuring a personal Duo device and pass it to the Duo client without an allowlist or explicit timeout. An authenticated remote attacker can make the server connect to chosen hosts over HTTPS on port 443 and tell failure modes apart, which exposes internal DNS and service reachability. Connections still require TLS certificate validation, and unresponsive targets can hold a server worker until the operating system timeout. This is classified as Server-Side Request Forgery (CWE-918).

Written with Claude Haiku 5.5 from the sources below · 2026-11-04

Description from the CNA

Psono Server CE && EE versions 0.1.0 through 7.2.3 accepted a user-controlled host when configuring a personal Duo device and passed it to the Duo client without an allowlist or explicit timeout. An authenticated remote attacker could cause the server to connect to selected hosts over HTTPS on port 443 and distinguish failure modes, providing an internal DNS and service-reachability oracle. Connections still required TLS certificate validation, and the flaw did not provide arbitrary protocol or port access. Unresponsive targets could also occupy a server worker until the operating-system timeout.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00242 15th percentileScored 2026-11-07
Fix Fixed Psono (esaqa GmbH): 7.2.4

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
esaqa GmbHPsono0.1.0 to before 7.2.47.2.4Patch availableCNA
  • Psono Vendoresaqa GmbH Affected 0.1.0 to before 7.2.4 Fixed in 7.2.4 Patch available CNA

Remediation

Upgrade esaqa GmbH Psono to version 7.2.4 or later, which fixes the flaw.

Written with Claude Haiku 5.5 from the sources below · 2026-11-04

  • Fix · CNA Psono (esaqa GmbH) Fixed in 7.2.4

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    esaqa Psono 7.2.4

    5 records Highest priority Priority LOW 5 LOW

    Other records, highest priority first

    • TI-2026-81017 WebAuthn assertion replay permits second-factor bypass in Psono ServerPriority LOW 29
    • TI-2026-81015 Device-code claim permits restricted token escalation in Psono ServerPriority LOW 29
    • TI-2026-81016 Psono file-transfer confusion allows unauthorized repository writesPriority LOW 24

Timeline

  1. 2026-10-27 Threatist record created from CVE-2026-117471
  2. 2026-10-27 Alias added: GHSA-q3ph-3gv2-g5wq
  3. 2026-10-27 Priority changed: MEDIUM → LOW
  4. 2026-11-04 CISA SSVC decision points changed

References

  • TI-2025-01732 Stored XSS in Psono-Client via Malicious Vault Entry URLs CVSS 4.0CRITICAL 9.3
  • TI-2026-81017 WebAuthn assertion replay permits second-factor bypass in Psono Server CVSS 3.1MEDIUM 6.5
  • TI-2026-81015 Device-code claim permits restricted token escalation in Psono Server CVSS 3.1MEDIUM 6.5
  • TI-2026-81016 Psono file-transfer confusion allows unauthorized repository writes CVSS 3.1MEDIUM 5.4
  • TI-2026-81021 URL prefix handling permits API key read-scope bypass in Psono Server CVSS 3.1MEDIUM 4.3

Sources