Every applicability statement published about this vulnerability, kept as each source wrote it rather than merged into one verdict. Where sources disagree, both positions are shown.
A statement that names no version covers the whole product, which is not the same as your version falling inside a range. Orderings marked best effort come from schemes with no published comparison algorithm; exact ones follow a published specification.
Precedence decides which claim wins when two sources describe the same product over the same version range. It is a property of the source, not of the claim, and changing it re-ranks the data without re-reading a single document.
| Product | Status | Versions | Remediation | Source | |
|---|---|---|---|---|---|
| red_hat_jboss_fuse_service_works_6:struts2-core struts2-core as a component of Red Hat JBoss Fuse Service Works 6 | not affected vulnerable code not present | struts2-core | not applicable | csaf_redhat | |
| https://github.com/apache/struts | affected | >= e5009a34202777b53c5dc36e020d0033aa8be027, <= 1ed29d508fc0a3762ad7d16336a71adcf69bd88d | none available | osv | |
| org.apache.struts:struts2-struts1-plugin | affected | <= 2.3.37 | none available | osv GHSA-29rm-6752-gvwv | |
| Apache Software Foundation/Apache Struts Apache Software Foundation · Apache Struts | affected | 2.1.x series | none available | cve_cna | |
| Apache Software Foundation/Apache Struts Apache Software Foundation · Apache Struts | affected | 2.3.x series | none available | cve_cna |
A claim with no version range is shown as written rather than expanded: a government catalog naming only a vendor and product is a real statement at zero granularity, and inventing bounds for it would put precision in the record that the source never offered.