Vulnerability Database

347,064

Total vulnerabilities in the database

Vulnerabilities for products matching "enterprise_linux"

Found 1 matching product.

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

redhat / enterprise_linux

3367 vulnerabilities found
Title Severity Exploit Date Affected Version
Medium April 3, 2018 4/3/18
== 7.4
== 7.0
== 6.0
== 7.5
== 7.6
Medium April 3, 2018 4/3/18
== 7.4
== 7.0
== 6.0
== 7.5
== 7.6
Medium April 3, 2018 4/3/18
== 7.4
== 7.0
== 6.0
== 7.5
== 7.6
Medium March 26, 2018 3/26/18
== 7.4
== 7.0
== 6.0
== 7.5
== 7.6
Medium March 26, 2018 3/26/18
== 7.4
== 7.0
== 6.0
== 7.5
== 7.6
Low March 26, 2018 3/26/18
== 7.4
== 7.0
== 6.0
== 7.5
== 7.6
Low March 26, 2018 3/26/18
== 7.4
== 7.0
== 6.0
== 7.5
== 7.6
High March 12, 2018 3/12/18
== 7.0
== 6.0
Medium March 12, 2018 3/12/18
== 7.0
== 6.0
Low March 9, 2018 3/9/18
== 7.0
== 6.0
Low March 2, 2018 3/2/18
== 7.0
Medium March 1, 2018 3/1/18
== 7.4
Medium February 16, 2018 2/16/18
== 7.0
High February 9, 2018 2/9/18
== 7.0
Low February 9, 2018 2/9/18
== 7.0
== 6.0
Low January 18, 2018 1/18/18
== 6.0
Low January 14, 2018 1/14/18
== 7.0
Low January 14, 2018 1/14/18
== 7.0
Low January 10, 2018 1/10/18
== 7.0
== 6.0
Low January 9, 2018 1/9/18
== 7.0
Low January 9, 2018 1/9/18
== 7.0
Low January 8, 2018 1/8/18
== 7.0
== 6.0
Medium December 29, 2017 12/29/17
== 7.0
== 6.0
Low December 29, 2017 12/29/17
== 7.0
High December 18, 2017 12/18/17
== 7.0
High December 18, 2017 12/18/17
== 7.0
Low December 7, 2017 12/7/17
== 7.0
== 6.0
Low November 30, 2017 11/30/17
== 7.0
Medium November 15, 2017 11/15/17
== 6.0
== 5.0
High October 5, 2017 10/5/17
== 7.0
== 6.0
== 5.0
High October 5, 2017 10/5/17
== 7.0
== 6.0
== 7.2
== 7.1
== 6.7
== 7.3
== 6.1
== 6.2
== 6.3
== 6.4
== 6.5
== 6.6
== 6.8
== 6.9
Low September 19, 2017 9/19/17
== 7.0
== 7.2
== 7.3
Low September 14, 2017 9/14/17
== 7.0
High August 19, 2017 8/19/17
== 7.0
High August 11, 2017 8/11/17
== 6.0
High August 11, 2017 8/11/17
== 6.0
Low August 10, 2017 8/10/17
== 6.0
Low July 17, 2017 7/17/17
== 5.11
Medium June 26, 2017 6/26/17
== 7.0
High June 19, 2017 6/19/17
== 5
== 7.0
== 6.0
High June 19, 2017 6/19/17
== 7.0
== 6.0
High May 9, 2017 5/9/17
== 6.0
High May 9, 2017 5/9/17
== 6.0
High May 9, 2017 5/9/17
== 6.0
High May 9, 2017 5/9/17
== 6.0
High May 9, 2017 5/9/17
== 6.0
High May 9, 2017 5/9/17
== 6.0
High May 9, 2017 5/9/17
== 6.0
Medium April 21, 2017 4/21/17
== 7.0
Low April 21, 2017 4/21/17
== 7.0

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.