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 | |
|---|---|---|---|---|---|
| North Grid Corporation/Proself Enterprise/Standard Edition North Grid Corporation · Proself Enterprise/Standard Edition | affected | Ver5.62 and earlier | none available | cve_cna | |
| North Grid Corporation/Proself Gateway Edition North Grid Corporation · Proself Gateway Edition | affected | Ver1.65 and earlier | none available | cve_cna | |
| North Grid Corporation/Proself Mail Sanitize Edition North Grid Corporation · Proself Mail Sanitize Edition | affected | Ver1.08 and earlier | none available | cve_cna | |
| northgrid/proself northgrid · proself | affected | <= 5.62 | none available | cve_adp | |
| northgrid/proself northgrid · proself | affected | <= 1.65 | none available | cve_adp | |
| northgrid/proself northgrid · proself | affected | <= 1.08 | none available | cve_adp |
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.