strongSwan 5.9.8 and 5.9.9 potentially allows remote code execution because it uses a variable named "public" for two different purposes within the same function. There is initially incorrect access control, later followed by an expired pointer dereference. One attack vector is sending an untrusted client certificate during EAP-TLS. A server is affected only if it loads plugins that implement TLS-based EAP methods (EAP-TLS, EAP-TTLS, EAP-PEAP, or EAP-TNC). This is fixed in 5.9.10.
oryginał ENCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HStrongswan
APPStrongswan5.9.85.9.9
Powiązane podatności
Buffer overflow w strongSwan umożliwiający zdalny RCE bez uwierzytelnienia
In strongSwan before 5.9.5, a malicious responder can send an EAP-Success message too early without actually a...
strongSwan 5.2.2 and 5.3.0 allows remote attackers to cause a denial of service (daemon crash) or execute arbi...
strongSwan versions 5.9.2 through 5.9.5 are affected by authorization bypass through improper validation of ce...
strongSwan before 5.9.8 allows remote attackers to cause a denial of service in the revocation plugin by sendi...