Vulnerabilities for products matching "suse_linux"
Found 2 matching products. Filters apply to all results.
You can search for specific versions with /product/suse_linux/1.2.3
suse / suse_linux
203 vulnerabilities found| Title | Severity | Exploit | Date | Affected Version |
|---|---|---|---|---|
|
|
High | January 22, 2010 1/22/10 |
== 10-sp3
|
|
|
|
High | July 5, 2009 7/5/09 |
== 11
|
|
|
|
High | September 22, 2008 9/22/08 |
*
|
|
|
|
High | November 29, 2007 11/29/07 |
*
|
|
|
|
High | October 16, 2007 10/16/07 |
== 10-sp1
|
|
|
|
Medium | October 14, 2007 10/14/07 |
== 10
|
|
|
|
High | October 14, 2007 10/14/07 |
== 10
|
|
|
|
Low | August 20, 2007 8/20/07 |
== 10
|
|
|
|
Low | August 17, 2007 8/17/07 |
*
|
|
|
|
Low | August 17, 2007 8/17/07 |
== 10
== 9.0
|
|
|
|
High | July 30, 2007 7/30/07 |
*
|
|
|
|
Low | May 14, 2007 5/14/07 |
== 9.0
== 8
== 1.0
|
|
|
|
High | January 24, 2007 1/24/07 |
== 9.3
<= 10.1
|
|
|
|
Low | December 20, 2006 12/20/06 |
== 10
|
|
|
|
High | October 31, 2006 10/31/06 |
== 10.0
== 9.3
== 9.2
== 10.1
|
|
|
|
Medium | September 12, 2006 9/12/06 |
== 10.0
== 9.3
== 9.2
== 10.1
|
|
|
|
Medium | June 1, 2006 6/1/06 |
== 9.0
|
|
|
|
Medium | June 1, 2006 6/1/06 |
== 9.0
|
|
|
|
High | March 21, 2006 3/21/06 |
== 10.0
|
|
|
|
Medium | February 23, 2006 2/23/06 |
== 9.3
|
|
|
|
Low | February 11, 2006 2/11/06 |
== 9.0
== 9.1
== 9.3
== 9.2
== 10.0
|
|
|
|
Low | January 31, 2006 1/31/06 |
== 9.1
== 9.3
== 9.2
== 10.0
== 1.0
|
|
|
|
Medium | December 31, 2005 12/31/05 |
== 9.0
== 9.1
== 10.0
== 9.3
== 9.2
== 1.0
|
|
|
|
High | December 31, 2005 12/31/05 |
== 9.0
== 9.1
== 10.0
== 9.3
== 9.2
== 1.0
|
|
|
|
Medium | December 31, 2005 12/31/05 |
== 9.0
== 9.1
== 10.0
== 9.3
== 9.2
== 1.0
|
|
|
|
Medium | December 31, 2005 12/31/05 |
== 9.0
== 8.0
== 9.1
== 10.0
== 9.3
== 8
== 1.0
== 9.2
== 8.2
|
|
|
|
Low | December 31, 2005 12/31/05 |
== 9.3
== 9.2
|
|
|
|
Low | December 31, 2005 12/31/05 |
== 9.3
== 9.2
|
|
|
|
Medium | December 31, 2005 12/31/05 |
== 9.3
|
|
|
|
Low | October 27, 2005 10/27/05 |
== 9.3
== 9.2
== 9.1
== 9.0
|
|
|
|
Medium | October 27, 2005 10/27/05 |
== 9.0
|
|
|
|
High | October 23, 2005 10/23/05 |
== 9.0
|
|
|
|
Low | October 5, 2005 10/5/05 |
*
|
|
|
|
Low | October 5, 2005 10/5/05 |
*
|
|
|
|
Low | October 5, 2005 10/5/05 |
*
|
|
|
|
Low | September 21, 2005 9/21/05 |
== 9.3
|
|
|
|
Low | August 5, 2005 8/5/05 |
== 9.0
== 9.3
== 9.2
== 8
== 1.0
== 9.1
|
|
|
|
Low | August 5, 2005 8/5/05 |
== 9.0
== 9.3
== 9.2
== 8
== 1.0
== 9.1
|
|
|
|
High | June 17, 2005 6/17/05 |
== 9.3
|
|
|
|
High | June 9, 2005 6/9/05 |
== 9.0
== 8
== 1.0
|
|
|
|
High | May 2, 2005 5/2/05 |
== 9.2
== 9.0
== 8.2
== 8.0
== 9.1
== 8.1
|
|
|
|
Low | May 2, 2005 5/2/05 |
== 9.0
== 9.2
== 8.2
== 8
== 1.0
== 9.1
== 8.1
|
|
|
|
High | May 2, 2005 5/2/05 |
== 9.2
== 9.0
== 8.2
== 8.0
== 9.1
== 8.1
|
|
|
|
Medium | April 27, 2005 4/27/05 |
== 9.2
== 9.0
== 8.2
== 8.0
== 9.1
== 8.1
|
|
|
|
High | April 27, 2005 4/27/05 |
== 1.0
== 2.0
== 3.0
== 4.0
== 4.2
== 4.3
== 4.4
== 4.4.1
== 5.0
== 5.1
== 5.2
== 5.3
== 6.0
== 6.1
== 6.1-alpha
== 6.2
== 6.3
== 6.3-alpha
== 6.4
== 6.4-alpha
== 7.0
== 7.0-alpha
== 7.1
== 7.1-alpha
== 7.2
== 7.3
== 8.0
== 8.1
== 8.2
== 9.0
== 9.1
== 9.2
|
|
|
|
High | April 14, 2005 4/14/05 |
== 9.2
== 9.0
== 8.2
== 8.0
== 9.1
== 8.1
|
|
|
|
High | April 14, 2005 4/14/05 |
== 9.2
== 9.0
== 8.2
== 8.0
== 9.1
== 8.1
|
|
|
|
Medium | April 14, 2005 4/14/05 |
== 9.2
== 9.0
== 8.2
== 8.0
== 9.1
== 8.1
|
|
|
|
Medium | April 14, 2005 4/14/05 |
== 9.2
== 9.0
== 8.2
== 8.0
== 9.1
== 8.1
|
|
|
|
Medium | April 14, 2005 4/14/05 |
== 9.2
== 9.0
== 8.2
== 8.0
== 9.1
== 8.1
|
novell / suse_linux
15 vulnerabilities found| Title | Severity | Exploit | Date | Affected Version |
|---|---|---|---|---|
|
|
Low | April 16, 2015 4/16/15 |
== 11.0-sp3
|
|
|
|
Low | April 16, 2015 4/16/15 |
== 11.0-sp3
|
|
|
|
High | July 29, 2013 7/29/13 |
== 11
|
|
|
|
Low | April 18, 2011 4/18/11 |
== 10-sp3
== 10-sp4
== 11-sp4
== 11-sp3
|
|
|
|
High | January 13, 2011 1/13/11 |
== 11-sp1
== 10-sp3
|
|
|
|
High | October 12, 2010 10/12/10 |
== 11-sp1
|
|
|
|
Medium | September 3, 2010 9/3/10 |
== 11
|
|
|
|
Low | October 23, 2009 10/23/09 |
== 11
== 10-sp2
|
|
|
|
Low | August 20, 2007 8/20/07 |
== 10.1
|
|
|
|
Low | August 17, 2007 8/17/07 |
== 10.0
== 10.1
|
|
|
|
High | March 6, 2007 3/6/07 |
== 10.0
== 10.1
|
|
|
|
Medium | February 23, 2006 2/23/06 |
== 10.0
|
|
|
|
Medium | December 31, 2005 12/31/05 |
== 10.0
|
|
|
|
Low | December 31, 2005 12/31/05 |
== 10.0
|
|
|
|
Low | October 27, 2005 10/27/05 |
== 10.0
|
Showing vulnerabilities for 2 products matching "suse_linux". Each product has independent pagination.
Deep Security Visibility Without the Complexity
SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.
- No setup fees
- 5-min deployment
- Cancel anytime
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.