CVE-2018-16152: 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…
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.8% (FIRST EPSS); higher than 79.8% of all records.
- 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.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: strongswan (Alpine:v3.10) 5.7.0-r0; strongswan (Alpine:v3.5) 5.5.3-r2; strongswan (Alpine:v3.7) 5.6.3-r1.
Low priority for now. Upgrade to strongswan (Alpine:v3.10) 5.7.0-r0; strongswan (Alpine:v3.5) 5.5.3-r2; strongswan (Alpine:v3.7) 5.6.3-r1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.8% · 79th percentile
- CWE
- CWE-347
Report tools
Action score
31
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.8%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| 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…40Plan
- 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…40Plan
- 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
Published before and after this one in the same product
- ← EarlierCVE-2018-10811Jun 19, 2018 · strongSwan 5.6.0 and older allows Remote Denial of Service because of Missing Initialization of a Variable.32Monitor
- ← EarlierCVE-2018-16151Sep 26, 2018 · 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…31Monitor
- Later →CVE-2018-17540Oct 3, 2018 · The gmp plugin in strongSwan before 5.7.1 has a Buffer Overflow via a crafted certificate.31Monitor
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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- 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.