opensymphony vulnerabilities
Recent CVEs affecting opensymphony products. 4 tracked.
opensymphony has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2011-05-13. Highest priority: CVE-2007-4556 (score 53/100).
- CVE-2011-2088 MEDIUM 5.0 DOWNGRADE DOWNGRADE XWork 2.2.1 in Apache Struts 2.2.1, and OpenSymphony XWork in OpenSymphony WebWork, allows remote attackers to
- CVE-2011-1772 LOW 2.6 DOWNGRADE MITIGATE Multiple cross-site scripting (XSS) vulnerabilities in XWork in Apache Struts 2.x before 2.2.3, and OpenSympho
- CVE-2008-6504 MEDIUM 5.0 DOWNGRADE DOWNGRADE ParametersInterceptor in OpenSymphony XWork 2.0.x before 2.0.6 and 2.1.x before 2.1.2, as used in Apache Strut
- CVE-2007-4556 MEDIUM 6.8 UPGRADE Struts support in OpenSymphony XWork before 1.2.3, and 2.x before 2.0.4, as used in WebWork and Apache Struts,
FAQ
How do I fix opensymphony vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is opensymphony being exploited right now?
None of the tracked opensymphony CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which opensymphony CVE should I patch first?
CVE-2007-4556 currently ranks highest (53/100): Struts support in OpenSymphony XWork before 1.2.3, and 2.x before 2.0.4, as used in WebWork and Apache Struts,.