Skip to content

strongSwan bug bounty programs

strongswan.org Updated

StrongSwan runs one public program: a Sorona bug bounty paying up to $1,500.

Top reward
$1,500
Sorona
Programs
1
1 pays cash
Targets in scope
7
2 types
Last change
None yet
Tracked since Nov 2026

Where to report

The one public program strongSwan runs.

Amounts are the top reward per severity in the currency each program pays. First response is the platform's measured average when it publishes one, else what the policy promises.

What is in scope

7 targets. 5 excluded.

  • https://www.strongswan.org

    Web

  • Credential and PKI handling in the pki tool and the credential plugins: X.509 chain building, CRL and OCSP processing, and the RSA and ECDSA verification paths

    Products and areas

  • Reports go to the strongSwan security address, which also serves as the project's OSS-Fuzz contact, and the object is the upstream strongSwan tree rather than a vendor's appliance fork or another IPsec implementation

    Products and areas

  • The authentication plugin family end to end, EAP-TLS, EAP-TTLS and EAP-MSCHAPv2 included, together with the identity-matching logic that turns an exchange into an authentication decision

    Products and areas

  • The charon daemon in full: the IKEv1 and IKEv2 message parsers reachable pre-authentication on UDP/500 and UDP/4500, and the state machine behind them

    Products and areas

  • The kernel interface plugins, kernel-netlink above all, and XFRM policy and SA installation, where a policy confusion becomes a traffic-selector bypass

    Products and areas

  • The vici and swanctl control interface and the legacy stroke socket

    Products and areas

No target matches. Try part of a host name, such as the company name.

Out of scope 5

Don't test these. A program can exclude a host another program covers; the program you report to decides.

  • Kernel XFRM and IPsec bugs, which belong to the Linux kernel scope row rather than to strongSwan

  • Libreswan and other IPsec implementations, which are separate projects with no OSS-Fuzz integration and no pathway

  • One-line fixes for non-exploitable crashes, which the Patch Rewards rules exclude

  • Vendor firmware forks shipped inside appliances rather than the upstream repository

  • Weak proposals or pre-shared keys the operator chose, which is configuration rather than a code defect

Recent changes

Reward and scope changes across every strongSwan program, newest first.

No changes recorded yet. New targets and reward moves show up here and in the RSS feed.

Recent CVEs

Published vulnerabilities in strongSwan products, from the NVD.

Search NVD
  • libcharon in strongSwan 5.9.7 through 6.0.7 mishandles behavioral workflow in the IKEv2 state machine. Because CREATE_CHILD_SA requests are mishandled, there can be an authentication bypass.

  • strongSwan 5.1.3 through 6.0.7 has an infinite loop in the x509 plugin's attribute certificate parser for ietfAttrSyntax.

  • libcharon in strongSwan 6.0.0 through 6.0.7 has a use-after-free in IKEv2 rekeying collision handling.

  • strongSwan 4.5.0 through 6.0.7 has Incorrect Access Control in the eap-ttls and eap-peap plugins because there can be a missing or mismatched inner EAP identity.

  • strongSwan 5.0.2 through 6.0.7 allows PKCS#7 certificate enumeration in the openssl plugin that leads to a lack of release of memory after its effective lifetime.

  • strongSwan 4.1.10 through 6.0.7 allows a NULL pointer dereference in the eap-aka plugin.

  • libcharon in strongSwan 4.1.2 through 6.0.7 has a missing release of memory after its effective lifetime in the IKE message parser.

  • strongSwan 4.6.2 through 6.0.7 has an infinite loop in PKCS#5 decryption.

About this page

This page gathers every public program listed under strongswan.org: platform programs, self-hosted policies and security.txt contacts. Each program's own policy decides what is in scope and what it pays; check it before you test.

Something wrong or missing? Report a correction.