CyberzSOC

Applicability
← Back to CVE-2016-4437

CVE-2016-4437

CVSS 9.8 In CISA KEV Apache

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.

Does it affect your version?

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.

What each source says

Red Hat CSAF/VEX
precedence 100 · revised 2025-11-21
4 affected 2 fixed
OSV.dev (incl. GHSA)
precedence 80 · revised 2026-07-08
3 affected 3 fixed
CVE List v5 (CNA container)
precedence 60 · revised 2025-10-21
1 affected

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.

Statements (13)

Product Status Versions Remediation Source
red_hat_jboss_a-mq_6:shiro-core shiro-core as a component of Red Hat JBoss A-MQ 6 affected no version stated vendor label: shiro-core none available fix in another branch csaf_redhat
red_hat_jboss_fuse_6:shiro-core shiro-core as a component of Red Hat JBoss Fuse 6 affected no version stated vendor label: shiro-core none available fix in another branch csaf_redhat
red_hat_jboss_fuse_service_works_6:shiro-core shiro-core as a component of Red Hat JBoss Fuse Service Works 6 affected no version stated vendor label: shiro-core none available fix in another branch csaf_redhat
red_hat_openshift_enterprise_2:shiro-core shiro-core as a component of Red Hat OpenShift Enterprise 2 affected no version stated vendor label: shiro-core none available fix in another branch csaf_redhat
Red Hat JBoss A-MQ 6.3 fixed no version stated vendor fix csaf_redhat
Red Hat JBoss Fuse 6.3 fixed no version stated vendor fix csaf_redhat
https://github.com/apache/aurora affected >= fc8697aa0fee97cb587f21334ca58b40546f3e76, < b009191cf66aa73c5ed85ccfd5d5e322efa11c74 vendor fix → b009191cf66aa73c5ed85ccfd5d5e322efa11c74 osv
https://github.com/apache/shiro affected < bf1e04fca099ca6fd1a9a16da1aea04a5bb8f404 vendor fix → bf1e04fca099ca6fd1a9a16da1aea04a5bb8f404 osv
org.apache.shiro:shiro-core affected < 1.2.5 vendor fix → 1.2.5 osv GHSA-p836-389h-j692
https://github.com/apache/aurora fixed b009191cf66aa73c5ed85ccfd5d5e322efa11c74 vendor fix → b009191cf66aa73c5ed85ccfd5d5e322efa11c74 osv
https://github.com/apache/shiro fixed bf1e04fca099ca6fd1a9a16da1aea04a5bb8f404 vendor fix → bf1e04fca099ca6fd1a9a16da1aea04a5bb8f404 osv
org.apache.shiro:shiro-core fixed 1.2.5 vendor fix → 1.2.5 osv GHSA-p836-389h-j692
n/a/n/a n/a · n/a affected no version stated vendor label: all versions 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.