CoreWCF.UnixDomainSocket
Affected
- introduced
0, fixed1.8.1(ecosystem)
Fixed versions
1.8.1
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-54776
CoreWCF: Unix Domain Socket PosixIdentity transport accepts connections that skip the security upgrade
Impact
A CoreWCF service hosted on Unix Domain Sockets with the PosixIdentity client credential type (UnixDomainSocketBinding with Security.Mode = TransportCredentialOnly and Security.Transport.ClientCredentialType = PosixIdentity) does not require the client to perform the application/unixposix stream upgrade before dispatching messages.
Patches
Fixed in CoreWCF v1.8.1 and v1.9.1
Workarounds
Restrict filesystem access to the UDS socket file using owner/group/mode (e.g. chmod 0660 plus a dedicated group) so that only the POSIX users who are already authorized to invoke the service can connect at all. This makes the missing-upgrade behaviour equivalent to the operating system’s filesystem permissions instead of relying on framing-layer identity checks.
Avoid relying on ServiceSecurityContext.PrimaryIdentity for authorization decisions, or back it up with an authentication-required authorization policy that rejects anonymous principals.
Medium Basis: The source's own band: MODERATE
0, fixed 1.8.1 (ecosystem)1.8.1
The export has no generic command for this ecosystem.
1.9.0, fixed 1.9.1 (ecosystem)1.9.1
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0