CVE-2009-0497
CVE-2009-0497 is a medium-severity vulnerability in Igniterealtime Openfire with a CVSS 2.0 base score of 5.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-22.
Key facts
- Severity: Medium (CVSS 2.0 base score 5.0)
- EPSS exploit prediction: 8% (95th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-22
- Affected product: Igniterealtime Openfire
- Published:
- Last modified:
Description
Directory traversal vulnerability in log.jsp in Ignite Realtime Openfire 3.6.2 allows remote attackers to read arbitrary files via a ..\ (dot dot backslash) in the log parameter.
Frequently asked questions
- What is CVE-2009-0497?
- Directory traversal vulnerability in log.jsp in Ignite Realtime Openfire 3.6.2 allows remote attackers to read arbitrary files via a ..\ (dot dot backslash) in the log parameter.
- How severe is CVE-2009-0497?
- CVE-2009-0497 has a CVSS 2.0 base score of 5.0, rated medium severity.
- Is CVE-2009-0497 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 8% (95th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2009-0497?
- CVE-2009-0497 affects Igniterealtime Openfire. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2009-0497?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- When was CVE-2009-0497 published?
- CVE-2009-0497 was published on 2009-02-10 and last updated on 2026-06-16.
References
- http://secunia.com/advisories/33452
- http://svn.igniterealtime.org/svn/repos/openfire/trunk/src/web/log.jsp
- http://www.coresecurity.com/content/openfire-multiple-vulnerabilities
- http://www.securityfocus.com/archive/1/499880/100/0/threaded
- http://www.securityfocus.com/bid/32945
- https://bugs.gentoo.org/show_bug.cgi?id=257585
- https://exchange.xforce.ibmcloud.com/vulnerabilities/47806
Affected products (1)
- cpe:2.3:a:igniterealtime:openfire:3.6.2:*:*:*:*:*:*:*
More vulnerabilities in Igniterealtime Openfire
- CVE-2024-25421 — Critical (CVSS 9.8): An issue in Ignite Realtime Openfire v.4.9.0 and before allows a remote attacker to escalate privileges via the…
- CVE-2021-45967 — Critical (CVSS 9.8): An issue was discovered in Pascom Cloud Phone System before 7.20.x. A configuration error between NGINX and a backend…
- CVE-2019-18394 — Critical (CVSS 9.8): A Server Side Request Forgery (SSRF) vulnerability in FaviconServlet.java in Ignite Realtime Openfire through 4.4.2…
- CVE-2023-32315 — High (CVSS 8.6): Openfire is an XMPP server licensed under the Open Source Apache License. Openfire's administrative console, a…
- CVE-2014-2741 — High (CVSS 7.8): nio/XMLLightweightParser.java in Ignite Realtime Openfire before 3.9.2 does not properly restrict the processing of…
- CVE-2014-3451 — High (CVSS 7.5): OpenFire XMPP Server before 3.10 accepts self-signed certificates, which allows remote attackers to perform unspecified…
All CVEs affecting Igniterealtime Openfire →
Other CWE-22 (Path Traversal) vulnerabilities
- CVE-2026-77312 — Critical (CVSS 10.0): Flyto2 Core is an execution kernel for automation and AI-agent workflows. Prior to 2.26.8, the earlier CVE-2026-67429…
- CVE-2026-121351 — Critical (CVSS 10.0): Adobe Connect is affected by an Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')…
- CVE-2026-121489 — Critical (CVSS 10.0): Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Apache Juneau. The…
- CVE-2026-122013 — Critical (CVSS 10.0): A vulnerability was detected in Comfast CF-WR632AX 2.6.0.1. Affected by this vulnerability is an unknown functionality…
- CVE-2026-61738 — Critical (CVSS 10.0): SOCFortress CoPilot focuses on providing a single pane of glass for all your security operations needs. Prior to…
- CVE-2026-112690 — Critical (CVSS 10.0): This issue was addressed with improved input validation. This issue is fixed in iOS 26.7.2 and iPadOS 26.7.2, iOS 27.2…