Описание
Shibboleth XMLTooling-C before 1.6.4, as used in Shibboleth Service Provider before 2.6.1.4 on Windows and other products, mishandles digital signatures of user data, which allows remote attackers to obtain sensitive information or conduct impersonation attacks via crafted XML data. NOTE: this issue exists because of an incomplete fix for CVE-2018-0486.
| Релиз | Статус | Примечание |
|---|---|---|
| artful | ignored | end of life |
| bionic | not-affected | 1.6.4-1ubuntu2 |
| devel | not-affected | 1.6.4-1ubuntu2 |
| esm-apps-legacy/xenial | released | 1.5.6-2ubuntu0.2 |
| esm-apps/bionic | not-affected | 1.6.4-1ubuntu2 |
| esm-apps/xenial | released | 1.5.6-2ubuntu0.2 |
| esm-infra-legacy/trusty | released | 1.5.3-2+deb8u3build0.14.04.1 |
| precise/esm | DNE | |
| trusty | released | 1.5.3-2+deb8u3build0.14.04.1 |
| trusty/esm | released | 1.5.3-2+deb8u3build0.14.04.1 |
Показывать по
6.4 Medium
CVSS2
6.5 Medium
CVSS3
Связанные уязвимости
Shibboleth XMLTooling-C before 1.6.4, as used in Shibboleth Service Provider before 2.6.1.4 on Windows and other products, mishandles digital signatures of user data, which allows remote attackers to obtain sensitive information or conduct impersonation attacks via crafted XML data. NOTE: this issue exists because of an incomplete fix for CVE-2018-0486.
Shibboleth XMLTooling-C before 1.6.4, as used in Shibboleth Service Provider before 2.6.1.4 on Windows and other products, mishandles digital signatures of user data, which allows remote attackers to obtain sensitive information or conduct impersonation attacks via crafted XML data. NOTE: this issue exists because of an incomplete fix for CVE-2018-0486.
Shibboleth XMLTooling-C before 1.6.4, as used in Shibboleth Service Pr ...
Shibboleth XMLTooling-C before 1.6.4, as used in Shibboleth Service Provider before 2.6.1.4 on Windows and other products, mishandles digital signatures of user data, which allows remote attackers to obtain sensitive information or conduct impersonation attacks via crafted XML data. NOTE: this issue exists because of an incomplete fix for CVE-2018-0486.
6.4 Medium
CVSS2
6.5 Medium
CVSS3