Swift Apple Swift

stack.watch can email you when security vulnerabilities are reported in Apple Swift. You can add multiple products that you use with Swift to create your own personal software stack watcher.

By the Year

In 2021 there have been 0 vulnerabilities in Apple Swift . Last year Swift had 1 security vulnerability published. Right now, Swift is on track to have less security vulnerabilities in 2021 than it did last year.

Year Vulnerabilities Average Score
2021 0 0.00
2020 1 7.50
2019 0 0.00
2018 1 8.80

It may take a day or so for new Swift vulnerabilities to show up. Additionally vulnerabilities may be tagged under a different product or component name.

Latest Apple Swift Security Vulnerabilities

A stack overflow issue existed in Swift for Linux

CVE-2020-9861 7.5 - High - November 02, 2020

A stack overflow issue existed in Swift for Linux. The issue was addressed with improved input validation for dealing with deeply nested malicious JSON input.

CVE-2020-9861 can be explotited with network access, and does not require authorization privledges or user interaction. This vulnerability is considered to have a low attack complexity. It has the highest possible exploitability rating (3.9). The potential impact of an exploit of this vulnerability is considered to have no impact on confidentiality and integrity, and a high impact on availability.

Out-of-bounds Write

An issue was discovered in certain Apple products

CVE-2018-4220 8.8 - High - June 08, 2018

An issue was discovered in certain Apple products. Swift before 4.1.1 Security Update 2018-001 is affected. The issue involves the "Swift for Ubuntu" component. It allows attackers to execute arbitrary code in a privileged context because write and execute permissions are enabled during library loading.

CVE-2018-4220 is exploitable with network access, requires user interaction. This vulnerability is considered to have a low attack complexity. It has an exploitability score of 2.8 out of four. The potential impact of an exploit of this vulnerability is considered to be very high.

Incorrect Permission Assignment for Critical Resource