Vulnerability Database

326,214

Total vulnerabilities in the database

Vulnerabilities for products matching "openfire"

Found 2 matching products. Filters apply to all results.

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

ignite_realtime / openfire

6 vulnerabilities found
Title Severity Exploit Date Affected Version
Low February 10, 2009 2/10/09
== 3.6.2
Low April 11, 2008 4/11/08
== 3.4.5
High June 1, 2007 6/1/07
== 3.2.0
== 3.0.1
== 2.6.1
== 3.2.2
== 3.2.3
== 3.1.0
== 3.2.1
== 3.2.4
== 2.6.0
<= 3.3.0
== 3.0.0
== 2.6.2
== 3.1.1
Low December 31, 2006 12/31/06
<= 3.5.2
== 2.6.0
Low December 31, 2005 12/31/05
== 2.2.2
Low December 31, 2005 12/31/05
== 2.3.0-beta_2

igniterealtime / openfire

37 vulnerabilities found
Title Severity Exploit Date Affected Version
Critical March 26, 2024 3/26/24
<= 4.9.0
High March 26, 2024 3/26/24
<= 4.9.0
High May 26, 2023 5/26/23
>= 3.10.0 < 4.6.8
>= 4.7.0 < 4.7.5
Critical March 18, 2022 3/18/22
< 4.5.0
== 4.5.0
Medium December 12, 2020 12/12/20
== 4.6.0
Medium December 12, 2020 12/12/20
== 4.6.0
Medium December 12, 2020 12/12/20
== 4.6.0
Medium December 12, 2020 12/12/20
== 4.6.0
Medium December 11, 2020 12/11/20
== 4.6.0
Medium September 2, 2020 9/2/20
== 4.5.1
Medium September 2, 2020 9/2/20
== 4.5.1
Medium September 2, 2020 9/2/20
== 4.5.1
Medium March 19, 2020 3/19/20
== 4.4.1
Medium March 19, 2020 3/19/20
== 4.4.1
Medium March 19, 2020 3/19/20
== 4.4.1
Medium March 18, 2020 3/18/20
== 4.4.1
Medium January 8, 2020 1/8/20
== 4.4.4
Medium January 8, 2020 1/8/20
== 4.4.4
Medium January 8, 2020 1/8/20
== 4.4.4
Medium January 8, 2020 1/8/20
== 4.4.4
Medium October 24, 2019 10/24/19
<= 4.4.2
Critical October 24, 2019 10/24/19
<= 4.4.2
Low August 23, 2019 8/23/19
< 4.4.1
Low June 13, 2018 6/13/18
== 3.7.1
Low October 26, 2017 10/26/17
<= 4.1.6
Medium August 18, 2017 8/18/17
<= 3.9.3
Medium October 5, 2015 10/5/15
== 3.10.2
Medium September 16, 2015 9/16/15
== 3.10.2
Low September 16, 2015 9/16/15
== 3.10.2
High April 11, 2014 4/11/14
<= 3.9.1
Low May 11, 2009 5/11/09
== 3.2.2
<= 3.6.3
== 3.4.2
== 3.0.0
== 3.0.1
== 3.2.1
== 3.4.4
== 3.1.0
== 3.4.0
== 3.6.0
== 3.2.3
== 3.4.5
== 3.3.2
== 3.2.0
== 3.5.0
== 3.4.3
== 2.6.1
== 3.6.1
== 3.6.0a
== 3.6.2
== 2.6.0
== 2.6.2
== 3.1.1
== 3.5.2
== 3.3.3
== 3.5.1
== 3.2.4
== 3.3.0
== 3.4.1
Medium May 11, 2009 5/11/09
< 3.6.5
High March 23, 2009 3/23/09
== 3.2.2
<= 3.6.0a
== 3.0.0
== 3.0.1
== 3.2.1
== 3.4.4
== 3.1.0
== 3.4.0
== 3.6.0
== 3.2.3
== 3.4.5
== 3.3.2
== 3.2.0
== 3.5.0
== 3.4.3
== 2.6.1
== 2.6.0
== 2.6.2
== 3.1.1
== 3.5.2
== 3.3.3
== 3.5.1
== 3.2.4
== 3.3.0
== 3.4.1
High March 23, 2009 3/23/09
== 3.2.2
<= 3.6.0a
== 3.0.0
== 3.0.1
== 3.2.1
== 3.4.4
== 3.1.0
== 3.4.0
== 3.6.0
== 3.2.3
== 3.4.5
== 3.3.2
== 3.2.0
== 3.5.0
== 3.4.3
== 2.6.1
== 2.6.0
== 2.6.2
== 3.1.1
== 3.5.2
== 3.3.3
== 3.5.1
== 3.2.4
== 3.3.0
== 3.4.1
Low March 23, 2009 3/23/09
== 3.2.2
<= 3.6.0a
== 3.0.0
== 3.0.1
== 3.2.1
== 3.4.4
== 3.1.0
== 3.4.0
== 3.6.0
== 3.2.3
== 3.4.5
== 3.3.2
== 3.2.0
== 3.5.0
== 3.4.3
== 2.6.1
== 2.6.0
== 2.6.2
== 3.1.1
== 3.5.2
== 3.3.3
== 3.5.1
== 3.2.4
== 3.3.0
== 3.4.1
Medium March 23, 2009 3/23/09
== 3.2.2
<= 3.6.0a
== 3.0.0
== 3.0.1
== 3.2.1
== 3.4.4
== 3.1.0
== 3.4.0
== 3.6.0
== 3.2.3
== 3.4.5
== 3.3.2
== 3.2.0
== 3.5.0
== 3.4.3
== 2.6.1
== 2.6.0
== 2.6.2
== 3.1.1
== 3.5.2
== 3.3.3
== 3.5.1
== 3.2.4
== 3.3.0
== 3.4.1
Medium February 10, 2009 2/10/09
== 3.6.2

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