Описание
HAPI FHIR HTTP authentication leak in redirects
Impact
When setting headers in HTTP requests, the internal HTTP client sends headers first to the host in the initial URL but also, if asked to follow redirects and a 30X HTTP response code is returned, to the host mentioned in URL in the Location: response header value.
Sending the same set of headers to subsequent hosts is a problem as this header often contains privacy sensitive information or data that could allow others to impersonate the client's request.
Patches
This issue has been patched in release 6.8.3
Workarounds
None.
Пакеты
ca.uhn.hapi.fhir:org.hl7.fhir.utilities
< 6.9.0
6.9.0
ca.uhn.hapi.fhir:org.hl7.fhir.convertors
< 6.9.0
6.9.0
ca.uhn.hapi.fhir:org.hl7.fhir.dstu2
< 6.9.0
6.9.0
ca.uhn.hapi.fhir:org.hl7.fhir.dstu3
< 6.9.0
6.9.0
ca.uhn.hapi.fhir:org.hl7.fhir.dstu3.support
< 6.9.0
6.9.0
ca.uhn.hapi.fhir:org.hl7.fhir.dstu2016may
< 6.9.0
6.9.0
ca.uhn.hapi.fhir:org.hl7.fhir.model
< 6.9.0
6.9.0
ca.uhn.hapi.fhir:org.hl7.fhir.r4
< 6.9.0
6.9.0
ca.uhn.hapi.fhir:org.hl7.fhir.r4b
< 6.9.0
6.9.0
ca.uhn.hapi.fhir:org.hl7.fhir.r5
< 6.9.0
6.9.0
ca.uhn.hapi.fhir:org.hl7.fhir.validation
< 6.9.0
6.9.0
ca.uhn.hapi.fhir:org.hl7.fhir.validation.cli
< 6.9.0
6.9.0
Связанные уязвимости
HAPI FHIR is a complete implementation of the HL7 FHIR standard for healthcare interoperability in Java. Prior to version 6.9.0, when setting headers in HTTP requests, the internal HTTP client sends headers first to the host in the initial URL but also, if asked to follow redirects and a 30X HTTP response code is returned, to the host mentioned in URL in the Location: response header value. Sending the same set of headers to subsequent hosts is a problem as this header often contains privacy sensitive information or data that could allow others to impersonate the client's request. This issue has been patched in release 6.9.0. No known workarounds are available.
HAPI FHIR is a complete implementation of the HL7 FHIR standard for healthcare interoperability in Java. Prior to version 6.9.0, when setting headers in HTTP requests, the internal HTTP client sends headers first to the host in the initial URL but also, if asked to follow redirects and a 30X HTTP response code is returned, to the host mentioned in URL in the Location: response header value. Sending the same set of headers to subsequent hosts is a problem as this header often contains privacy sensitive information or data that could allow others to impersonate the client's request. This issue has been patched in release 6.9.0. No known workarounds are available.