Vulnerability Database

328,409

Total vulnerabilities in the database

Vulnerabilities for products matching "systemd"

Found 2 matching products. Filters apply to all results.

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

systemd_project / systemd

48 vulnerabilities found
Title Severity Exploit Date Affected Version
Low May 30, 2025 5/30/25
< 252.37
>= 253 < 253.32
>= 254 < 254.25
>= 255 < 255.19
>= 256 < 256.14
>= 257 < 257.6
Medium December 23, 2023 12/23/23
== 25
Medium June 13, 2023 6/13/23
== 253
Medium June 13, 2023 6/13/23
== 253
Medium June 13, 2023 6/13/23
== 253
High March 3, 2023 3/3/23
< 246.7
Medium January 11, 2023 1/11/23
>= 246 < 253
Medium November 23, 2022 11/23/22
>= 250 <= 251
== 252-rc1
== 252-rc2
Medium November 8, 2022 11/8/22
<= 251
Critical September 9, 2022 9/9/22
== 240
Medium August 23, 2022 8/23/22
>= 240 < 250.2
Medium July 20, 2021 7/20/21
>= 247 < 247.8
< 246.15
>= 248 < 248.5
>= 249 < 249.1
Medium May 10, 2021 5/10/21
== 245
Medium June 3, 2020 6/3/20
<= 245
High March 31, 2020 3/31/20
<= 244
Medium March 11, 2020 3/11/20
== 37
Low January 21, 2020 1/21/20
< 243
Critical October 30, 2019 10/30/19
>= 239 < 244
Low September 4, 2019 9/4/19
== 240
Low May 17, 2019 5/17/19
== 242
High April 26, 2019 4/26/19
< 242
High April 26, 2019 4/26/19
< 242
High April 9, 2019 4/9/19
== 242-rc1
== 242-rc2
== 242-rc3
<= 241
Medium March 21, 2019 3/21/19
== 239
Low January 14, 2019 1/14/19
< 237
High January 11, 2019 1/11/19
<= 240
High January 11, 2019 1/11/19
<= 240
Low January 11, 2019 1/11/19
>= 221 <= 239
High October 26, 2018 10/26/18
<= 239
High October 26, 2018 10/26/18
<= 239
High October 26, 2018 10/26/18
>= 235 < 240
Medium February 16, 2018 2/16/18
< 234
High February 13, 2018 2/13/18
<= 237
High January 29, 2018 1/29/18
< 237
High October 26, 2017 10/26/17
== 228
== 229
== 224
== 225
== 223
== 232
== 234
== 230
== 231
== 226
== 227
== 235
== 233
High September 25, 2017 9/25/17
== 223
Critical July 7, 2017 7/7/17
>= 229 < 234
High June 28, 2017 6/28/17
>= 223 <= 233
High May 24, 2017 5/24/17
<= 233
High January 23, 2017 1/23/17
== 228
Low October 13, 2016 10/13/16
== 209
== 213
== 229
== 214
Low October 13, 2016 10/13/16
<= 231
Medium April 18, 2014 4/18/14
<= 037
== 23
== 22
== 21
== 20
== 27
== 26
== 25
== 24
== 15
== 14
== 13
== 12
== 19
== 18
== 17
== 16
== 7
== 6
== 5
== 4
== 11
== 10
== 9
== 8
== 3
== 2
== 1
== 36
== 31
== 30
== 29
== 28
== 35
== 34
== 33
== 32
High October 28, 2013 10/28/13
< 190
Medium October 28, 2013 10/28/13
< 239
Low October 28, 2013 10/28/13
< 194
Medium October 28, 2013 10/28/13
< 194
Medium October 3, 2013 10/3/13
<= 207

linux / systemd

1 vulnerabilities found
Title Severity Exploit Date Affected Version
Low July 12, 2012 7/12/12
== 43

Showing vulnerabilities for 2 products matching "systemd". 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.