Skip to main content
cve.nowby Sazabi
← Maven
MavenPackage

ca.uhn.hapi.fhir:org.hl7.fhir.validation.cli

6 known vulnerabilities (6 high), with the versions each affects and the releases that fix them.

Latest release
5.0.0 (May 12, 2020): affected by 6 advisories
Newest unaffected release
Every release is affected by at least one advisory
Advisories
6 · 6 high
Dependents
0
Releases
7 since 4.0.0 (Aug 14, 2019)
Registry
Maven Central
Releases read
Nov 8, 2026

Version timeline

Every release cve.now has on record, lowest version on the left; each bar is a run of versions an advisory affects.

Advisories 6

  • HAPI FHIR: SHCParser DEFLATE infinite loop causes denial of service

    Affected: fixed in 6.9.12.

    No fix released. The advisory names 6.9.12 as the fix, which the registry doesn't have yet. The latest release, 5.0.0, is still affected.

  • HAPI FHIR: SHCParser unbounded DEFLATE decompression causes denial of service

    Affected: through 5.0.0.

    No fix released. The latest release, 5.0.0, is still affected.

  • HAPI FHIR: ReDoS via FHIRPath matches()/replaceMatches() in FHIR Validator HTTP Endpoint

    Affected: from 6.9.5, fixed in 6.9.9; fixed in 6.9.4.2.

    No fix released. The advisory names 6.9.4.2 and 6.9.9 as the fix, which the registry doesn't have yet. The latest release, 5.0.0, is still affected.

  • HAPI FHIR: ReDoS via FHIRPath matches()/replaceMatches() in FHIR Validator HTTP Endpoint

    Affected: fixed in 6.9.7.

    No fix released. The advisory names 6.9.7 as the fix, which the registry doesn't have yet. The latest release, 5.0.0, is still affected.

  • HAPI FHIR: DSTU2 FHIRPathEngine.matches() missing RegexTimeout protection allows ReDoS

    Affected: fixed in 6.9.10.

    No fix released. The advisory names 6.9.10 as the fix, which the registry doesn't have yet. The latest release, 5.0.0, is still affected.

  • HAPI FHIR HTTP authentication leak in redirects

    Affected: fixed in 6.9.0.

    No fix released. The advisory names 6.9.0 as the fix, which the registry doesn't have yet. The latest release, 5.0.0, is still affected.