| identity: Does this identifier describe a vulnerability at all? the first rule that matches decides |
| 1 |
rejected |
no match |
|
CVE Program withdrawal of this identifier |
| scope: Is it a vulnerability Waratek protects? the first rule that matches decides |
| 2 |
armr-patch-file |
no match |
|
An ARMR patch file on disk for this CVE |
| 3 |
armr-secure-rule-file |
no match |
|
An ARMR security-rule template on disk for this CVE |
| 4 |
manual-classification |
no match |
|
A researcher's recorded decision for this specific CVE |
| 5 |
manual classification |
no match |
|
Manual classification of this CVE in the legacy dataset |
| 6 |
non-java-upstream |
no match |
|
A root cause in non-Java code: an OS kernel, a C library, or a bundled runtime |
| 7 |
oracle-component |
no match |
|
The defect being in a component of a tracked product the agent does not reach: JavaFX, the Java SE installer, the JInitiator browser plug-in, the native WebLogic proxy plug-in, or a native part of Oracle Application Server or Collaboration Suite (HTTP Server, Web Cache, Internet Directory, mail and calendar servers). Oracle gives these no CPE of their own and names them only in the description. |
| 8 |
java-client-side |
no match |
|
Oracle's own risk-matrix note saying the CVE is reached only through untrusted code in the Java sandbox (applets, Web Start) or only through a client installation of Java, so a server running its own trusted code is not exposed |
| 9 |
osv-maven |
no match |
|
An OSV.dev record of this CVE affecting a package published to Maven Central. When every such package is one business applications do not use (Minecraft mods and launchers, Fastjson) and no tracked product is named by CPE, it settles the CVE as Outside Waratek scope instead |
| 10 |
cna-maven-package |
no match |
|
An affected Maven artifact named by the CNA itself |
| 11 |
known-cpe-product |
matched |
In scope |
Matches known products: oracle/bi_publisher |
| 12 |
cna-cpe-product |
not reached |
|
A CPE the CNA published naming a tracked product. Oracle publishes these on advisory day, months before NVD. |
| 13 |
oracle-advisory-family |
not reached |
|
A tracked product family named in Oracle's own risk matrix. CPE cannot carry a suite name, only a module. |
| 14 |
cna-named-product |
not reached |
|
A tracked product named in words by the CVE's own CNA, on a record with no CPE yet. Apache and Eclipse publish these on advisory day, before NVD adds CPE data. |
| 15 |
non-deployable-product |
not reached |
|
The only affected product being a sealed appliance image, where Java runs but no -javaagent can be attached |
| 16 |
unmatched-product |
not reached |
|
No tracked product matched above, and none present at all |
| disposition: What do we do about one that is? every rule runs |
| 17 |
patch-hint |
no match |
|
A reference pointing at the upstream fix: a commit, a PR, a Red Hat bug |
| 18 |
open-source-maven |
no match |
|
The affected package being open source on Maven, so the fix can be read |
| 19 |
poc-derivable |
withheld |
|
VulnCheck KEV-listed (seen by Shadowserver honeypots on 328 day(s) from 2024-01-22 to 2026-11-10) but no PoC artifact is indexed — exploitation is reported, yet there is nothing published to reverse-engineer a rule from |
| 20 |
no-exploit |
withheld |
|
VulnCheck KEV-listed (seen by Shadowserver honeypots on 328 day(s) from 2024-01-22 to 2026-11-10) — exploitation is reported in the wild, so this cannot be resolved as having no published exploit regardless of public POC availability |
| 21 |
secure-rule-match |
no match |
|
A vulnerability class already blocked by an ARMR security rule |
| 22 |
exploited-no-fix-or-poc decided it |
matched |
Mitigation candidate |
VulnCheck KEV reports exploitation (seen by Shadowserver honeypots on 328 day(s) from 2024-01-22 to 2026-11-10). No upstream fix, no open-source Maven package, and no PoC is published. |
| 23 |
below-action-threshold |
no match |
|
Severity is HIGH — only MEDIUM/LOW are deprioritized |
| 24 |
no-exploit-published |
no match |
|
A CISA or VulnCheck KEV listing, a CISA verdict of active exploitation, a reviewed exploit catalogue, or a GitHub PoC with 5 or more stars carries this CVE — exploit code is in use or published, so it stays a candidate |