Skip to content

Latest commit

 

History

History
67 lines (54 loc) · 3.04 KB

SECURITY.md

File metadata and controls

67 lines (54 loc) · 3.04 KB
Raw

Security

This document specifies the security process for the SwiftNIO project.

Versions

The SwiftNIO core team will address security vulnerabilities in all SwiftNIO 2.x versions. Since support for some Swift versions was dropped during the lifetime of SwiftNIO 2, patch releases will be created for the last supported SwiftNIO versions that supported older Swift versions. If a hypothetical security vulnerability was introduced in 2.10.0, then SwiftNIO core team would create the following patch releases:

  • NIO 2.29. + plus next patch release to address the issue for projects that support Swift 5.0 and 5.1
  • NIO 2.39. + plus next patch release to address the issue for projects that support Swift 5.2 and 5.3
  • NIO 2.42. + plus next patch release to address the issue for projects that support Swift 5.4 and later
  • mainline + plus next patch release to address the issue for projects that support Swift 5.5.2 and later

SwiftNIO 1.x is considered end of life and will not receive any security patches.

Disclosures

Private Disclosure Process

The SwiftNIO core team asks that known and suspected vulnerabilities be privately and responsibly disclosed by emailing [email protected] with the details usually included with bug reports. Do not file a public issue.

When to report a vulnerability

  • You think you have discovered a potential security vulnerability in SwiftNIO or any of the SwiftNIO projects.
  • You are unsure how a vulnerability affects SwiftNIO or any of the SwiftNIO projects.

What happens next?

  • A member of the team will acknowledge receipt of the report within 3 working days (United States). This may include a request for additional information about reproducing the vulnerability.
  • We will privately inform the Swift Server Work Group (SSWG) of the vulnerability within 10 days of the report as per their security guidelines.
  • Once we have identified a fix we may ask you to validate it. We aim to do this within 30 days. In some cases this may not be possible, for example when the vulnerability exists at the protocol level and the industry must coordinate on the disclosure process.
  • If a CVE number is required, one will be requested from MITRE providing you with full credit for the discovery.
  • We will decide on a planned release date and let you know when it is.
  • Prior to release, we will inform major dependents that a security-related patch is impending.
  • Once the fix has been released we will publish a security advisory on GitHub and the SSWG will announce the vulnerability on the Swift forums.