In verify_emsa_pkcs1_signature() in gmp_rsa_public_key.c in the gmp plugin in strongSwan 4.x and 5.x before 5.7.0, the RSA implementation ba
In verify_emsa_pkcs1_signature() in gmp_rsa_public_key.c in the gmp plugin in strongSwan 4.x and 5.x before 5.7.0, the RSA implementation based on GMP does not reject excess data in the digestAlgorithm.parameters field during PKCS#1 v1.5 signature verification. Consequently, a remote attacker can forge signatures when small public exponents are being used, which could lead to impersonation when only an RSA signature is used for IKEv2 authentication. This is a variant of CVE-2006-4790 and CVE-2014-1568.
- Published
- Sep 26, 2018
- Updated
- Jun 16, 2026
- EPSS
- 1.9% · 79th percentile
- CWE
- CWE-347
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.9%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| strongswan | strongswan | cpe:2.3:a:strongswan:strongswan |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canonical ubuntu linux14.04
- canonical ubuntu linux16.04
- canonical ubuntu linux18.04
- debian debian linux8.0
- debian debian linux9.0
- strongswan strongswan4.0.0 and later · up to 4.6.4 inclusive
- strongswan strongswan5.0.0 and later · before 5.7.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | strongswan | from 4.0.0 · before 5.7.0-r0 | 5.7.0-r0 |
| Alpine:v3.5 | strongswan | from 4.0.0 · before 5.5.3-r2 | 5.5.3-r2 |
| Alpine:v3.7 | strongswan | from 4.0.0 · before 5.6.3-r1 | 5.6.3-r1 |
| Alpine:v3.8 | strongswan | from 4.0.0 · before 5.6.3-r2 | 5.6.3-r2 |
| Debian:12 | strongswan | before 5.7.0-1 | 5.7.0-1 |
| Debian:8 | strongswan | before 5.2.1-6+deb8u7 | 5.2.1-6+deb8u7 |
| Debian:9 | strongswan | before 5.5.1-4+deb9u3 | 5.5.1-4+deb9u3 |
| openSUSE:Leap 15.0 | strongswan | before 5.6.0-lp150.3.3.1 | 5.6.0-lp150.3.3.1 |
| openSUSE:Leap 15.1 | strongswan | before 5.6.0-lp151.4.3.1 | 5.6.0-lp151.4.3.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 | strongswan | before 5.6.0-4.3.2 | 5.6.0-4.3.2 |
| SUSE:Linux Enterprise Point of Sale 11 SP3 | strongswan | before 4.4.0-6.36.12.1 | 4.4.0-6.36.12.1 |
| SUSE:OpenStack Cloud 7 | strongswan | before 5.1.3-26.13.1 | 5.1.3-26.13.1 |
Same product
strongswan: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-41913strongSwan before 5.9.12 has a buffer overflow and possible unauthenticated remote code execution via a DH public value that exceeds the int40Plan
- CVE-2023-26463strongSwan 5.9.8 and 5.9.9 potentially allows remote code execution because it uses a variable named "public" for two different purposes wit40Plan
- CVE-2015-3991strongSwan 5.2.2 and 5.3.0 allows remote attackers to cause a denial of service (daemon crash) or execute arbitrary code.40Plan
- CVE-2021-45079In strongSwan before 5.9.5, a malicious responder can send an EAP-Success message too early without actually authenticating the client and (37Monitor
- CVE-2026-25075strongSwan 4.5.0 < 6.0.5 EAP-TTLS AVP Parsing Integer Underflow34Monitor
- CVE-2025-62291In the eap-mschapv2 plugin (client-side) in strongSwan before 6.0.3, a malicious EAP-MSCHAPv2 server can send a crafted message of size 6 th32Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:strongswan | 5.7.0-r0 · Alpine:v3.10 | Package registry (OSV) |
| debian:strongswan | 5.7.0-1 · Debian:12 | Package registry (OSV) |
| opensuse:strongswan | 5.6.0-lp150.3.3.1 · openSUSE:Leap 15.0 | Package registry (OSV) |
| suse:strongswan | 5.6.0-4.3.2 · SUSE:Linux Enterprise Module for Basesystem 15 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-347 · Improper Verification of Cryptographic SignatureCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
nvd-secondary
Root cause
The verifier takes the algorithm to verify with from the token’s own header. Untrusted data ends up deciding its own verification rule.
The bug in code
The whole CWE-347 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const claims = jwt.verify(token, publicKey);Fixed
const claims = jwt.verify(token, publicKey, { algorithms: ["RS256"], issuer: "https://id.example.com", audience: "portal",});Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- lists.opensuse.org/opensuse-security-announce/2019-11/msg00077.html
- lists.opensuse.org/opensuse-security-announce/2019-12/msg00001.html
- lists.opensuse.org/opensuse-security-announce/2020-03/msg00047.html
- lists.debian.org/debian-lts-announce/2018/09/msg00032.html
- security.gentoo.org/glsa/201811-16
- usn.ubuntu.com/3771-1/
- www.debian.org/security/2018/dsa-4305
- www.strongswan.org/blog/2018/09/24/strongswan-vulnerability-%28cve-2018-16151%2C-cve-2018-16152%29.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.