Vulnerability Database

328,409

Total vulnerabilities in the database

Vulnerabilities for products matching "openssl"

Found 8 matching products. Filters apply to all results.

You can search for specific versions with /product/openssl/1.2.3

openssl / openssl

260 vulnerabilities found
Title Severity Exploit Date Affected Version
CVE-2021-3712
High August 24, 2021 8/24/21
>= 1.0.2 < 1.0.2za
>= 1.1.1 < 1.1.1l
CVE-2021-3449
Medium March 25, 2021 3/25/21
>= 1.1.1 < 1.1.1k
CVE-2021-3450
High March 25, 2021 3/25/21
>= 1.1.1h < 1.1.1k
CVE-2021-23839
Low February 16, 2021 2/16/21
>= 1.0.2s <= 1.0.2x
CVE-2021-23840
High February 16, 2021 2/16/21
>= 1.0.2 < 1.0.2y
>= 1.1.1 < 1.1.1j
CVE-2021-23841
Medium February 16, 2021 2/16/21
>= 1.0.2 < 1.0.2y
>= 1.1.1 < 1.1.1j
CVE-2020-1971
Medium December 8, 2020 12/8/20
>= 1.0.2 < 1.0.2x
>= 1.1.1 < 1.1.1i
CVE-2020-1968
Low September 9, 2020 9/9/20
>= 1.0.2 <= 1.0.2v
CVE-2020-1967
High April 21, 2020 4/21/20
>= 1.1.1d <= 1.1.1f
CVE-2019-1551
Medium December 6, 2019 12/6/19
>= 1.0.2 <= 1.0.2t
>= 1.1.1 <= 1.1.1d
CVE-2019-1547
Low September 10, 2019 9/10/19
>= 1.1.1 <= 1.1.1c
>= 1.0.2 <= 1.0.2s
>= 1.1.0 <= 1.1.0k
CVE-2019-1549
Medium September 10, 2019 9/10/19
>= 1.1.1 <= 1.1.1c
CVE-2019-1563
Low September 10, 2019 9/10/19
>= 1.1.1 <= 1.1.1c
>= 1.0.2 <= 1.0.2s
>= 1.1.0 <= 1.1.0k
CVE-2019-1552
Low July 30, 2019 7/30/19
>= 1.1.1 <= 1.1.1c
>= 1.0.2 <= 1.0.2s
>= 1.1.0 <= 1.1.0k
CVE-2019-1543
Medium March 6, 2019 3/6/19
>= 1.1.1 <= 1.1.1b
>= 1.1.0 <= 1.1.0j
CVE-2019-1559
Medium February 27, 2019 2/27/19
>= 1.0.2 < 1.0.2r
CVE-2018-5407
Low November 15, 2018 11/15/18
>= 1.0.2 < 1.0.2q
>= 1.1.0 < 1.1.0i
CVE-2018-0734
Medium October 30, 2018 10/30/18
>= 1.0.2 <= 1.0.2p
>= 1.1.0 <= 1.1.0i
== 1.1.1
CVE-2018-0735
Medium October 29, 2018 10/29/18
>= 1.1.0 <= 1.1.0i
== 1.1.1
CVE-2016-7056
Low September 10, 2018 9/10/18
<= 1.0.1u
CVE-2018-0732
High June 12, 2018 6/12/18
>= 1.0.2 <= 1.0.2o
>= 1.1.0 <= 1.1.0h
CVE-2018-0737
Low April 16, 2018 4/16/18
>= 1.0.2b <= 1.0.2o
>= 1.1.0 <= 1.1.0h
CVE-2018-0733
Low March 27, 2018 3/27/18
>= 1.1.0 <= 1.1.0g
CVE-2018-0739
Low March 27, 2018 3/27/18
>= 1.0.2b <= 1.0.2n
>= 1.1.0 <= 1.1.0g
CVE-2017-3737
Low December 7, 2017 12/7/17
== 1.0.2e
== 1.0.2j
== 1.0.2b
== 1.0.2g
== 1.0.2h
== 1.0.2c
== 1.0.2f
== 1.0.2i
== 1.0.2d
== 1.0.2k
== 1.0.2l
== 1.0.2m
CVE-2017-3738
Medium December 7, 2017 12/7/17
== 1.0.2a
== 1.0.2e
== 1.0.2j
== 1.0.2b
== 1.0.2g
== 1.0.2h
== 1.0.2c
== 1.0.2-beta3
== 1.0.2-beta1
== 1.0.2
== 1.0.2f
== 1.0.2-beta2
== 1.0.2i
== 1.0.2d
== 1.0.2k
== 1.0.2l
== 1.0.2m
== 1.1.0e
== 1.1.0f
== 1.1.0c
== 1.1.0b
== 1.1.0d
== 1.1.0
== 1.1.0a
== 1.1.0g
CVE-2016-8610
High November 13, 2017 11/13/17
== 0.9.8
== 1.0.1
>= 1.0.2 <= 1.0.2h
== 1.1.0
CVE-2017-3736
Low November 2, 2017 11/2/17
>= 1.1.0 < 1.1.0g
>= 1.0.2 < 1.0.2m
CVE-2017-3735
Medium August 28, 2017 8/28/17
== 1.1.0e
== 0.9.8ze
== 1.0.2a
== 0.9.8b
== 1.0.1j
== 0.9.7l
== 0.9.8m
== 1.1.0f
== 1.0.0n
== 1.0.1-beta2
== 0.9.8c
== 1.0.0c
== 1.0.0i
== 1.0.0-beta1
== 1.0.1h
== 0.9.8n
== 1.0.0-beta2
== 0.9.8p
== 1.0.2e
== 1.0.2j
== 1.0.0m
== 1.0.2b
== 1.0.1c
== 0.9.7j
== 0.9.8e
== 0.9.8u
== 0.9.8za
== 1.0.1g
== 0.9.8g
== 1.0.0h
== 0.9.8k
== 0.9.8m-beta1
== 0.9.8d
== 1.0.0-beta3
== 1.0.0e
== 1.0.1-beta3
== 1.0.0f
== 0.9.8j
== 1.1.0c
== 1.0.0d
== 0.9.7k
== 1.0.0j
== 0.9.8s
== 1.0.0p
== 1.0.1a
== 1.0.1-beta1
== 1.0.0s
== 1.0.2h
== 1.0.0o
== 0.9.8l
== 0.9.8zc
== 1.0.1d
== 1.0.0k
== 0.9.8r
== 1.0.2c
== 0.9.8t
== 1.0.0-beta4
== 0.9.8z
== 1.1.0b
== 1.1.0d
== 0.9.8a
== 1.1.0
== 1.0.2-beta3
== 0.9.7m
== 1.0.2-beta1
== 1.0.1k
== 1.0.0
== 1.0.1b
== 1.1.0a
== 0.9.8zb
== 0.9.8o
== 0.9.8q
== 0.9.8w
== 1.0.1e
== 1.0.0-beta5
== 1.0.1l
== 0.9.8
== 1.0.1f
== 1.0.0l
== 0.9.8v
== 1.0.2
== 1.0.0r
== 0.9.8i
== 0.9.8f
== 0.9.8y
== 1.0.0a
== 1.0.0q
== 0.9.8h
== 0.9.8zg
== 1.0.2f
== 0.9.8x
== 1.0.1i
== 1.0.0b
== 1.0.2-beta2
== 1.0.1
== 1.0.2i
== 1.0.0g
== 1.0.2d
== 1.0.2k
== 1.0.2l
CVE-2016-7055
Medium May 4, 2017 5/4/17
>= 1.0.2 < 1.0.2k
>= 1.1.0 < 1.1.0c
CVE-2016-7053
Medium May 4, 2017 5/4/17
== 1.1.0b
== 1.1.0
== 1.1.0a
CVE-2016-7054
Medium May 4, 2017 5/4/17
== 1.1.0b
== 1.1.0
== 1.1.0a
CVE-2017-3730
Medium May 4, 2017 5/4/17
== 1.1.0
== 1.1.0a
== 1.1.0b
== 1.1.0c
CVE-2017-3731
High May 4, 2017 5/4/17
== 1.1.0c
== 1.1.0b
== 1.1.0a
== 1.0.2a
== 1.0.2e
== 1.0.2j
== 1.0.2b
== 1.0.2h
== 1.0.2c
== 1.0.2-beta3
== 1.0.2-beta1
== 1.0.2
== 1.0.2f
== 1.0.2-beta2
== 1.0.2i
== 1.0.2d
CVE-2017-3732
Medium May 4, 2017 5/4/17
== 1.0.2a
== 1.0.2e
== 1.0.2b
== 1.1.0c
== 1.0.2h
== 1.0.2c
== 1.1.0b
== 1.0.2-beta3
== 1.0.2-beta1
== 1.1.0a
== 1.0.2
== 1.0.2f
== 1.0.2-beta2
== 1.0.2i
== 1.0.2d
CVE-2017-3733
Medium May 4, 2017 5/4/17
== 1.1.0
== 1.1.0a
== 1.1.0b
== 1.1.0c
== 1.1.0d
CVE-2016-7052
High September 26, 2016 9/26/16
== 1.0.2i
CVE-2016-6309
High September 26, 2016 9/26/16
== 1.1.0a
CVE-2016-6308
High September 26, 2016 9/26/16
== 1.1.0
CVE-2016-6307
Low September 26, 2016 9/26/16
== 1.1.0
CVE-2016-6306
Medium September 26, 2016 9/26/16
== 1.0.1m
== 1.0.1j
== 1.0.1-beta2
== 1.0.1h
== 1.0.1r
== 1.0.1c
== 1.0.1g
== 1.0.1-beta3
== 1.0.1a
== 1.0.1-beta1
== 1.0.1d
== 1.0.1t
== 1.0.1p
== 1.0.1k
== 1.0.1b
== 1.0.1n
== 1.0.1q
== 1.0.1e
== 1.0.1l
== 1.0.1f
== 1.0.1s
== 1.0.1o
== 1.0.1i
== 1.0.1
== 1.0.2a
== 1.0.2e
== 1.0.2b
== 1.0.2h
== 1.0.2c
== 1.0.2-beta3
== 1.0.2-beta1
== 1.0.2
== 1.0.2f
== 1.0.2-beta2
== 1.0.2d
CVE-2016-6305
Medium September 26, 2016 9/26/16
== 1.1.0
CVE-2016-6304
High September 26, 2016 9/26/16
== 1.0.2a
== 1.0.2e
== 1.0.2b
== 1.0.2h
== 1.0.2c
== 1.0.2-beta3
== 1.0.2-beta1
== 1.0.2
== 1.0.2f
== 1.0.2-beta2
== 1.0.2d
== 1.1.0
== 1.0.1m
== 1.0.1j
== 1.0.1-beta2
== 1.0.1h
== 1.0.1r
== 1.0.1c
== 1.0.1g
== 1.0.1-beta3
== 1.0.1a
== 1.0.1-beta1
== 1.0.1d
== 1.0.1t
== 1.0.1p
== 1.0.1k
== 1.0.1b
== 1.0.1n
== 1.0.1q
== 1.0.1e
== 1.0.1l
== 1.0.1f
== 1.0.1s
== 1.0.1o
== 1.0.1i
== 1.0.1
CVE-2016-6303
Critical September 16, 2016 9/16/16
== 1.0.1m
== 1.0.2a
== 1.0.1j
== 1.0.1h
== 1.0.2e
== 1.0.1r
== 1.0.2b
== 1.0.1c
== 1.0.1g
== 1.0.2g
== 1.0.1a
== 1.0.2h
== 1.0.1d
== 1.0.1t
== 1.0.2c
== 1.0.1p
== 1.0.1k
== 1.0.1b
== 1.0.1n
== 1.0.1q
== 1.0.1e
== 1.0.1l
== 1.0.1f
== 1.0.1s
== 1.0.1o
== 1.0.2
== 1.0.2f
== 1.0.1i
== 1.0.1
== 1.0.2d
CVE-2016-6302
Medium September 16, 2016 9/16/16
== 1.0.1m
== 1.0.2a
== 1.0.1j
== 1.0.1h
== 1.0.2e
== 1.0.1r
== 1.0.2b
== 1.0.1c
== 1.0.1g
== 1.0.2g
== 1.0.1a
== 1.0.2h
== 1.0.1d
== 1.0.1t
== 1.0.2c
== 1.0.1p
== 1.0.1k
== 1.0.1b
== 1.0.1n
== 1.0.1q
== 1.0.1e
== 1.0.1l
== 1.0.1f
== 1.0.1s
== 1.0.1o
== 1.0.2
== 1.0.2f
== 1.0.1i
== 1.0.1
== 1.0.2d
CVE-2016-2182
High September 16, 2016 9/16/16
== 1.0.1m
== 1.0.2a
== 1.0.1j
== 1.0.1h
== 1.0.2e
== 1.0.1r
== 1.0.2b
== 1.0.1c
== 1.0.1g
== 1.0.2g
== 1.0.1a
== 1.0.2h
== 1.0.1d
== 1.0.1t
== 1.0.2c
== 1.0.1p
== 1.0.1k
== 1.0.1b
== 1.0.1n
== 1.0.1q
== 1.0.1e
== 1.0.1l
== 1.0.1f
== 1.0.1s
== 1.0.1o
== 1.0.2
== 1.0.2f
== 1.0.1i
== 1.0.1
== 1.0.2d
CVE-2016-2181
Medium September 16, 2016 9/16/16
== 1.0.1m
== 1.0.2a
== 1.0.1j
== 1.0.1h
== 1.0.2e
== 1.0.1r
== 1.0.2b
== 1.0.1c
== 1.0.1g
== 1.0.2g
== 1.0.1a
== 1.0.2h
== 1.0.1d
== 1.0.1t
== 1.0.2c
== 1.0.1p
== 1.0.1k
== 1.0.1b
== 1.0.1n
== 1.0.1q
== 1.0.1e
== 1.0.1l
== 1.0.1f
== 1.0.1s
== 1.0.1o
== 1.0.2
== 1.0.2f
== 1.0.1i
== 1.0.1
== 1.0.2d
CVE-2016-2179
Medium September 16, 2016 9/16/16
== 1.0.1m
== 1.0.2a
== 1.0.1j
== 1.0.1h
== 1.0.2e
== 1.0.1r
== 1.0.2b
== 1.0.1c
== 1.0.1g
== 1.0.2g
== 1.0.1a
== 1.0.2h
== 1.0.1d
== 1.0.1t
== 1.0.2c
== 1.0.1p
== 1.0.1k
== 1.0.1b
== 1.0.1n
== 1.0.1q
== 1.0.1e
== 1.0.1l
== 1.0.1f
== 1.0.1s
== 1.0.1o
== 1.0.2
== 1.0.2f
== 1.0.1i
== 1.0.1
== 1.0.2d
CVE-2016-2183
High September 1, 2016 9/1/16
== 1.0.1m
== 1.0.2a
== 1.0.1j
== 1.0.1h
== 1.0.2e
== 1.0.1r
== 1.0.2b
== 1.0.1c
== 1.0.1g
== 1.0.1a
== 1.0.2h
== 1.0.1d
== 1.0.1t
== 1.0.2c
== 1.0.1p
== 1.0.1k
== 1.0.1b
== 1.0.1n
== 1.0.1q
== 1.0.1e
== 1.0.1l
== 1.0.1f
== 1.0.1o
== 1.0.2f
== 1.0.1i
== 1.0.2d
CVE-2016-2180
Medium August 1, 2016 8/1/16
== 1.0.1m
== 1.0.2a
== 1.0.1j
== 1.0.1h
== 1.0.2e
== 1.0.1r
== 1.0.2b
== 1.0.1c
== 1.0.1g
== 1.0.2g
== 1.0.1a
== 1.0.2h
== 1.0.1d
== 1.0.1t
== 1.0.2c
== 1.0.1p
== 1.0.1k
== 1.0.1b
== 1.0.1n
== 1.0.1q
== 1.0.1e
== 1.0.1l
== 1.0.1f
== 1.0.1s
== 1.0.1o
== 1.0.2
== 1.0.2f
== 1.0.1i
== 1.0.1
== 1.0.2d

Showing vulnerabilities for 8 products matching "openssl". Each product has independent pagination.

Frequently Asked Questions

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.