How should we interpret CVSS severity scores?

CVSS estimates technical severity, but it does not automatically equal business risk. Prioritize using context like internet exposure, asset criticality, known exploitation, 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.

Vulnerability Database

Q: What is a Vulnerability (CVE) and why does it matter?

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.

Q: What's the difference between a vulnerability, an exploit, and a zero-day?

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. Risk increases sharply when exploitation becomes reliable or widespread.

Q: Why do vulnerabilities keep reappearing in our environment?

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.

Q: How do we prioritize remediation without burning out the team?

Use a 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 so remediation is steady, not reactive.

Q: How can SynScan help reduce vulnerability risk over time?

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.

328,409

Total vulnerabilities in the database

Vulnerabilities for products matching "spring_framework"

Found 3 matching products. Filters apply to all results.

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

springsource / spring_framework

5 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2014-0054	Medium	April 17, 2014 4/17/14	== 3.0.0-m2 == 3.0.1 == 3.0.0-rc3 == 3.0.5 == 4.0.0-rc1 == 3.0.2 == 3.0.0-m3 == 3.0.0-rc2 == 3.0.0-m1 == 4.0.1 == 3.0.4 == 3.0.0-rc1 == 3.0.3 == 3.2.5 == 3.0.0.m1 == 3.0.0-m4 == 3.2.6 == 3.0.0 == 3.0.0.m2
CVE-2013-7315	Medium	January 23, 2014 1/23/14	== 3.0.0-m2 == 3.0.1 == 3.0.0-rc3 == 3.0.5 == 3.0.2 == 3.0.0-m3 == 3.0.0-rc2 == 3.0.0-m1 == 3.0.4 == 3.0.0-rc1 == 3.0.3 == 3.0.0.m1 == 3.0.0-m4 == 3.0.0 == 3.0.0.m2
CVE-2013-4152	Medium	January 23, 2014 1/23/14	== 3.0.0-m2 == 3.0.1 == 3.0.0-rc3 == 3.0.5 == 3.0.2 == 3.0.0-m3 == 3.0.0-rc2 == 3.0.0-m1 == 3.0.4 == 3.0.0-rc1 == 3.0.3 == 3.0.0.m1 == 3.0.0-m4 == 3.0.0 == 3.0.0.m2
CVE-2011-2730	High	December 5, 2012 12/5/12	== 2.5.0 == 3.0.1 == 2.5.3 == 3.0.2 == 2.5.5 == 2.5.6 <= 2.5.7_sr01 == 2.5.0-rc1 == 3.0.4 == 2.5.4 == 2.5.0-rc2 <= 3.0.5 == 3.0.3 == 2.5.2 == 2.5.7 == 3.0.0 == 2.5.1
CVE-2010-1622	Medium	June 21, 2010 6/21/10	== 2.5.0 == 3.0.1 == 2.5.3 == 3.0.2 == 2.5.5 == 2.5.6 == 2.5.4 == 2.5.2 == 2.5.7 == 3.0.0 == 2.5.1

vmware / spring_framework

43 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2024-38820	Low	October 18, 2024 10/18/24	>= 6.1.0 < 6.1.14 >= 6.0.0 < 6.0.25 >= 5.3.0 < 5.3.41
CVE-2024-38808	Low	August 20, 2024 8/20/24	>= 5.3.0 < 5.3.39
CVE-2024-22259	High	March 16, 2024 3/16/24	< 5.3.33 >= 6.0.0 < 6.0.18 >= 6.1.0 < 6.1.5
CVE-2024-22233	High	January 22, 2024 1/22/24	== 6.1.2 == 6.0.15
CVE-2023-34053	Medium	November 28, 2023 11/28/23	>= 6.0.0 < 6.0.14
CVE-2023-20863	Medium	April 13, 2023 4/13/23	>= 6.0.0 < 6.0.8 >= 5.3.0 < 5.3.27 >= 5.2.0 < 5.2.24
CVE-2023-20860	High	March 27, 2023 3/27/23	>= 5.3.0 < 5.3.26 >= 6.0.0 < 6.0.7
CVE-2023-20861	Medium	March 23, 2023 3/23/23	>= 6.0.0 <= 6.0.6 >= 5.3.0 <= 5.3.25 <= 5.2.22
CVE-2022-22970	Medium	May 12, 2022 5/12/22	>= 5.3.0 <= 5.3.19 <= 5.2.21
CVE-2022-22971	Medium	May 12, 2022 5/12/22	>= 5.2.0 <= 5.2.21 >= 5.3.0 <= 5.3.19
CVE-2022-22968	Medium	April 14, 2022 4/14/22	< 5.2.0 >= 5.2.0 <= 5.2.20 >= 5.3.0 <= 5.3.18
CVE-2022-22950	Medium	April 1, 2022 4/1/22	< 5.2.20 >= 5.3.0 < 5.3.17
CVE-2022-22965	Critical	April 1, 2022 4/1/22	>= 5.3.0 < 5.3.18 < 5.2.20
CVE-2021-22060	Low	January 10, 2022 1/10/22	>= 5.3.0 <= 5.3.13 >= 5.2.0 <= 5.2.18
CVE-2021-22096	Low	October 28, 2021 10/28/21	>= 5.2.0 <= 5.2.17 >= 5.3.0 <= 5.3.10
CVE-2021-22118	High	May 27, 2021 5/27/21	>= 5.2.0 < 5.2.15 >= 5.3.0 < 5.3.7
CVE-2020-5421	Medium	September 19, 2020 9/19/20	>= 5.1.0 < 5.1.18 >= 5.2.0 < 5.2.9 >= 5.0.0 < 5.0.19 < 4.3.29
CVE-2020-5397	Medium	January 17, 2020 1/17/20	>= 5.2.0 < 5.2.3
CVE-2020-5398	High	January 17, 2020 1/17/20	>= 5.2.0 < 5.2.3 >= 5.0.0 < 5.0.16 >= 5.1.0 < 5.1.13
CVE-2016-1000027	Critical	January 2, 2020 1/2/20	< 6.0.0
CVE-2018-15801	High	December 19, 2018 12/19/18	>= 5.1.0 < 5.1.2
CVE-2018-15756	High	October 18, 2018 10/18/18	>= 4.2.0 < 4.3.20 >= 5.0.0 < 5.0.10 == 5.1.0
CVE-2018-11039	Medium	June 25, 2018 6/25/18	>= 5.0.0 < 5.0.7 < 4.3.18
CVE-2018-11040	High	June 25, 2018 6/25/18	>= 5.0.0 < 5.0.7 < 4.3.18
CVE-2018-1257	Medium	May 11, 2018 5/11/18	< 4.3.17 >= 5.0.0 < 5.0.6
CVE-2018-1258	High	May 11, 2018 5/11/18	== 5.0.5
CVE-2018-1275	Critical	April 11, 2018 4/11/18	>= 5.0.0 < 5.0.5 >= 4.3.0 < 4.3.16
CVE-2018-1270	Critical	April 6, 2018 4/6/18	< 4.3.16 >= 5.0.0 < 5.0.5
CVE-2018-1271	Medium	April 6, 2018 4/6/18	>= 5.0.0 < 5.0.5 >= 4.3.0 < 4.3.15
CVE-2018-1272	High	April 6, 2018 4/6/18	>= 4.3.0 < 4.3.15 >= 5.0 < 5.0.5
CVE-2018-1199	Medium	March 16, 2018 3/16/18	>= 5.0.0 < 5.0.3 >= 4.3.0 < 4.3.14
CVE-2014-0225	Medium	May 25, 2017 5/25/17	== 3.2.2 == 3.2.1 == 3.2.8 == 3.2.7 == 3.2.4 == 3.2.3 == 3.2.6 == 3.2.5 == 3.0.1 == 3.0.7 == 3.0.6 == 3.1.0-rc1 == 3.0.3 == 3.0.2 == 3.0.5 == 3.0.4 == 3.2.0-rc1 == 3.1.4 == 3.2.0-rc2-a == 3.2.0-rc2 == 3.1.1 == 3.1.0-rc2 == 3.1.3 == 3.1.2 == 4.0.3 == 4.0.2 == 4.0.4 == 4.0.0-rc1 == 4.0.1 == 4.0.0-rc2
CVE-2015-5211	Critical	May 25, 2017 5/25/17	== 3.2.2 == 3.2.1 == 3.2.8 == 3.2.7 == 3.2.10 == 3.2.9 == 3.2.4 == 3.2.3 == 3.2.6 == 3.2.5 == 4.0.5 == 4.0.7 == 4.0.6 == 3.2.12 == 3.2.11 == 3.2.13 == 4.0.9 == 4.0.8 == 4.0.3 == 4.0.2 == 4.0.4 == 4.0.1 == 3.2.14 == 4.1.6 == 4.1.5 == 4.1.7 == 4.2.1 == 4.1.1 == 4.1.2 == 4.1.3 == 4.1.4 == 3.2.0 == 4.0.0 == 4.1.0 == 4.2.0
CVE-2016-5007	Medium	May 25, 2017 5/25/17	== 3.2.2 == 3.2.1 == 3.2.8 == 3.2.7 == 3.2.10 == 3.2.9 == 3.2.4 == 3.2.3 == 3.2.6 == 3.2.5 == 4.0.5 == 4.0.7 == 4.0.6 == 3.2.12 == 3.2.11 == 3.2.13 == 4.0.9 == 4.0.8 == 4.0.3 == 4.0.2 == 4.0.4 == 4.0.1 == 3.2.15 == 3.2.17 == 3.2.16 == 3.2.14 == 3.2.18 == 4.1.6 == 4.1.5 == 4.2.9 == 4.1.9 == 4.1.8 == 4.1.7 == 4.2.1 == 4.2.2 == 4.2.8 == 4.2.3 == 4.2.4 == 4.2.5 == 4.2.7 == 4.2.6 == 4.1.1 == 4.1.2 == 4.1.3 == 4.1.4
CVE-2016-9878	Medium	December 29, 2016 12/29/16	== 3.2.2 == 3.2.1 == 3.2.8 == 3.2.7 == 3.2.10 == 3.2.9 == 3.2.4 == 3.2.3 == 3.2.6 == 3.2.5 == 3.2.12 == 3.2.11 == 3.2.13 == 3.2.15 == 3.2.17 == 3.2.16 == 3.2.14 == 4.3.3 == 4.2.1 == 4.3.2 == 4.2.2 == 4.2.8 == 4.2.3 == 4.3.4 == 4.2.4 == 4.3.1 == 4.2.5 == 4.2.7 == 4.2.6
CVE-2015-3192	Low	July 12, 2016 7/12/16	== 3.2.2 == 3.2.1 == 3.2.8 == 3.2.7 == 3.2.10 == 3.2.9 == 3.2.4 == 3.2.3 == 3.2.6 == 3.2.5 == 3.2.12 == 3.2.11 == 3.2.13 == 4.1.6 == 4.1.5 == 4.1.1 == 4.1.2 == 4.1.3 == 4.1.4
CVE-2015-0201	Medium	March 10, 2015 3/10/15	== 4.1.1 == 4.1.2 == 4.1.3 == 4.1.4
CVE-2014-3625	Medium	November 20, 2014 11/20/14	>= 3.0.4 <= 3.0.7
CVE-2014-0054	Medium	April 17, 2014 4/17/14	<= 3.2.7 == 3.0.6 == 3.0.7 == 3.1.0 == 3.1.1 == 3.1.2 == 3.1.3 == 3.1.4 == 3.2.0 == 3.2.1 == 3.2.2 == 3.2.3 == 3.2.4 == 4.0.0-milestone1 == 4.0.0-milestone2
CVE-2013-6429	Medium	January 26, 2014 1/26/14	== 4.0.0-rc1 == 4.0.0-milestone2 == 4.0.0-milestone1
CVE-2013-7315	Medium	January 23, 2014 1/23/14	<= 3.2.3 == 3.0.6 == 3.0.7 == 3.1.0 == 3.1.1 == 3.1.2 == 3.1.3 == 3.1.4 == 3.2.0 == 3.2.1 == 3.2.2 == 4.0.0-milestone1 == 4.0.0-milestone2
CVE-2013-4152	Medium	January 23, 2014 1/23/14	<= 3.2.3 == 3.0.6 == 3.0.7 == 3.1.0 == 3.1.1 == 3.1.2 == 3.1.3 == 3.1.4 == 3.2.0 == 3.2.1 == 3.2.2 == 4.0.0-milestone1
CVE-2011-2894	Medium	October 4, 2011 10/4/11	>= 3.0.0 <= 3.0.5

pivotal_software / spring_framework

10 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2013-6430	Medium	January 10, 2020 1/10/20	>= 3.0.0 < 3.2.2
CVE-2014-0225	Medium	May 25, 2017 5/25/17	== 3.2.0 == 4.0.0 == 3.1.0 == 3.0.0
CVE-2016-5007	Medium	May 25, 2017 5/25/17	== 4.1.0 == 3.2.0 == 4.2.0 == 4.0.0
CVE-2016-9878	Medium	December 29, 2016 12/29/16	== 4.2.0 == 4.3.0 <= 3.2.0
CVE-2015-3192	Low	July 12, 2016 7/12/16	== 3.2.0 == 4.1.0
CVE-2015-0201	Medium	March 10, 2015 3/10/15	== 4.1.0
CVE-2014-3578	Medium	February 19, 2015 2/19/15	>= 3.2.0 < 3.2.9 >= 4.0.0 < 4.0.5
CVE-2014-3625	Medium	November 20, 2014 11/20/14	>= 3.1.0 <= 3.1.4 >= 3.2.0 < 3.2.12 >= 4.0.0 < 4.0.8 >= 4.1.0 < 4.1.2
CVE-2014-1904	Low	March 20, 2014 3/20/14	>= 4.0.0 < 4.0.2 >= 3.0.0 < 3.2.8
CVE-2013-6429	Medium	January 26, 2014 1/26/14	>= 3.0.0 <= 3.2.4

Showing vulnerabilities for 3 products matching "spring_framework". 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

Book a Demo

Frequently Asked Questions

What is a Vulnerability (CVE) and why does it matter?

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.