| 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 |
matched |
In scope |
Maven packages: org.bouncycastle:bcprov-jdk14, org.bouncycastle:bcprov-jdk15to18, org.bouncycastle:bcprov-jdk18on, org.bouncycastle:bcprov-debug-jdk14, org.bouncycastle:bcprov-debug-jdk15to18, org.bouncycastle:bcprov-debug-jdk18on, org.bouncycastle:bcprov-ext-jdk14, org.bouncycastle:bcprov-ext-jdk15to18, org.bouncycastle:bcprov-ext-jdk18on, org.bouncycastle:bcprov-ext-debug-jdk14, org.bouncycastle:bcprov-ext-debug-jdk15to18, org.bouncycastle:bcprov-ext-debug-jdk18on, org.bouncycastle:bcprov-debug-jdk15on, org.bouncycastle:bcprov-jdk15on |
| 10 |
cna-maven-package |
not reached |
|
An affected Maven artifact named by the CNA itself |
| 11 |
known-cpe-product |
not reached |
|
An NVD CPE naming a product ARMR tracks |
| 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 |
matched |
Mitigation candidate |
References include candidate fix URL (commit tier): https://github.com/bcgit/bc-java/commit/701686cb0184cd9ae103c801b3581fdf95c6d4f3 |
| 18 |
open-source-maven |
skipped |
|
The affected package being open source on Maven, so the fix can be read |
| 19 |
poc-derivable |
skipped |
|
An indexed exploit clearing the evidence bar to reverse-engineer, where there is no source to read |
| 20 |
no-exploit |
skipped |
|
Nothing to build a rule from yet: no published exploit, no CISA record of exploitation and no source-level change to read |
| 21 |
secure-rule-match |
no match |
|
A vulnerability class already blocked by an ARMR security rule |
| 22 |
exploited-no-fix-or-poc |
skipped |
|
Somebody exploiting this CVE (a CISA or VulnCheck KEV listing, or a CISA verdict of active exploitation), with no fix, source code or PoC to build a rule from |
| 23 |
below-action-threshold |
no match |
|
Severity is CRITICAL — only MEDIUM/LOW are deprioritized |
| 24 |
no-exploit-published decided it |
matched |
No exploit published |
No exploit code has been published, and an upstream fix path does exist, so the remediation half of the candidacy still holds. |
