Skip to content
Fencer Intel
medium 5.3

CVE-2018-6459 json

The rsa_pss_params_parse function in libstrongswan/credentials/keys/signature_params.c in strongSwan 5.6.1 allows remote attackers to cause…

published 2018-02-20 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-18216

cvss
5.3
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 64%
public exploits
0
none known

Summary

The rsa_pss_params_parse function in libstrongswan/credentials/keys/signature_params.c in strongSwan 5.6.1 allows remote attackers to cause a denial of service via a crafted RSASSA-PSS signature that lacks a mask generation function parameter.

Patch / fix

  • strongswan Debian 14, Debian 13, Debian 12 5.6.2-1

debian advisories DEBIAN-CVE-2018-6459

  • strongswan SLE Module for Basesystem 15 SP1 5.8.2-4.6.14

suse advisories SUSE-SU-2020:0743-1

  • strongswan openSUSE Tumbleweed 5.9.0-1.9
  • strongswan openSUSE Leap 15.1 5.8.2-lp151.4.6.1

opensuse advisories openSUSE-SU-2024:11411-1openSUSE-SU-2020:0403-1

  • strongswan Arch Linux 5.6.2-1

arch linux advisories AVG-625

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-6459 updated cvss 7.5

strongswan: Insufficient Input Validation in RSASSA-PSS Signature Parser

  • Red Hat Enterprise Linux 7 strongimcv
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.05% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 5.3 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-347 Improper Verification of Cryptographic Signature

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.