CVE-2022-23632

Traefik is an HTTP reverse proxy and load balancer. Prior to version 2.6.1, Traefik skips the router transport layer security (TLS) configuration when the host header is a fully qualified domain name (FQDN). For a request, the TLS configuration choice can be different than the router choice, which implies the use of a wrong TLS configuration. When sending a request using FQDN handled by a router configured with a dedicated TLS configuration, the TLS configuration falls back to the default configuration that might not correspond to the configured one. If the CNAME flattening is enabled, the selected TLS configuration is the SNI one and the routing uses the CNAME value, so this can skip the expected TLS configuration. Version 2.6.1 contains a patch for this issue. As a workaround, one may add the FDQN to the host rule. However, there is no workaround if the CNAME flattening is enabled.

CVSS v3 7.5 HIGH
CVSS v2.0 6.8 MEDIUM

7.5^/10

CVSS v3 : HIGH

Vector :

Exploitability : 3.9 / Impact : 3.6

Attack Vector NETWORK

Attack Complexity LOW

Privileges Required NONE

User Interaction NONE

Confidentiality Impact NONE

Integrity Impact HIGH

Availability Impact NONE

Scope UNCHANGED

6.8^/10

CVSS v2.0 : MEDIUM

Vector : AV:N/AC:M/Au:N/C:P/I:P/A:P

Exploitability : 8.6 / Impact : 6.4

Access Vector NETWORK

Access Complexity MEDIUM

Authentication NONE

Confidentiality Impact PARTIAL

Integrity Impact PARTIAL

Availability Impact PARTIAL

References

Link	Resource
https://github.com/traefik/traefik/pull/8764	Issue Tracking Patch Third Party Advisory
https://github.com/traefik/traefik/releases/tag/v2.6.1	Release Notes Third Party Advisory
https://github.com/traefik/traefik/security/advisories/GHSA-hrhx-6h34-j5hc	Patch Third Party Advisory
https://www.oracle.com/security-alerts/cpujul2022.html	Third Party Advisory

Configurations

Configuration 1 (hide)

cpe:2.3:a:traefik:traefik:*:*:*:*:*:*:*:*

Configuration 2 (hide)

cpe:2.3:a:oracle:communications_unified_inventory_management:7.5.0:*:*:*:*:*:*:*

History

No history.

Information

Published : 2022-02-17 15:15

Updated : 2022-11-23 19:22

NVD link : CVE-2022-23632

Mitre link : CVE-2022-23632

CVE.ORG link : CVE-2022-23632

JSON object : View

Products Affected

traefik

traefik

oracle

communications_unified_inventory_management

CWE

CWE-295

Improper Certificate Validation

{"id": "CVE-2022-23632", "cveTags": [], "metrics": {"cvssMetricV2": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"version": "2.0", "baseScore": 6.8, "accessVector": "NETWORK", "vectorString": "AV:N/AC:M/Au:N/C:P/I:P/A:P", "authentication": "NONE", "integrityImpact": "PARTIAL", "accessComplexity": "MEDIUM", "availabilityImpact": "PARTIAL", "confidentialityImpact": "PARTIAL"}, "acInsufInfo": false, "impactScore": 6.4, "baseSeverity": "MEDIUM", "obtainAllPrivilege": false, "exploitabilityScore": 8.6, "obtainUserPrivilege": false, "obtainOtherPrivilege": false, "userInteractionRequired": false}], "cvssMetricV31": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.5, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 3.6, "exploitabilityScore": 3.9}, {"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.4, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.2, "exploitabilityScore": 2.2}]}, "published": "2022-02-17T15:15:09.580", "references": [{"url": "https://github.com/traefik/traefik/pull/8764", "tags": ["Issue Tracking", "Patch", "Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/traefik/traefik/releases/tag/v2.6.1", "tags": ["Release Notes", "Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/traefik/traefik/security/advisories/GHSA-hrhx-6h34-j5hc", "tags": ["Patch", "Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://www.oracle.com/security-alerts/cpujul2022.html", "tags": ["Third Party Advisory"], "source": "security-advisories@github.com"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Primary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-295"}]}], "descriptions": [{"lang": "en", "value": "Traefik is an HTTP reverse proxy and load balancer. Prior to version 2.6.1, Traefik skips the router transport layer security (TLS) configuration when the host header is a fully qualified domain name (FQDN). For a request, the TLS configuration choice can be different than the router choice, which implies the use of a wrong TLS configuration. When sending a request using FQDN handled by a router configured with a dedicated TLS configuration, the TLS configuration falls back to the default configuration that might not correspond to the configured one. If the CNAME flattening is enabled, the selected TLS configuration is the SNI one and the routing uses the CNAME value, so this can skip the expected TLS configuration. Version 2.6.1 contains a patch for this issue. As a workaround, one may add the FDQN to the host rule. However, there is no workaround if the CNAME flattening is enabled."}, {"lang": "es", "value": "Traefik es un proxy inverso HTTP y equilibrador de carga. En versiones anteriores a 2.6.1, Traefik omit\u00eda la configuraci\u00f3n de seguridad de la capa de transporte (TLS) del router cuando el encabezado del host era un nombre de dominio completo (FQDN). Para una petici\u00f3n, la elecci\u00f3n de la configuraci\u00f3n TLS puede ser diferente a la elecci\u00f3n del router, lo que implica el uso de una configuraci\u00f3n TLS err\u00f3nea. Cuando es enviada una petici\u00f3n usando FQDN manejada por un router configurado con una configuraci\u00f3n TLS dedicada, la configuraci\u00f3n TLS vuelve a la configuraci\u00f3n por defecto que puede no corresponder a la configurada. Si el aplanamiento de CNAME est\u00e1 habilitado, la configuraci\u00f3n TLS seleccionada es la de SNI y el enrutamiento usa el valor de CNAME, por lo que puede omitir la configuraci\u00f3n TLS esperada. La versi\u00f3n 2.6.1 contiene un parche para este problema. Como medida de mitigaci\u00f3n, puede a\u00f1adirse el FDQN a la regla de host. Sin embargo, no es presentada una medida de mitigaci\u00f3n si el aplanamiento CNAME est\u00e1 habilitado"}], "lastModified": "2022-11-23T19:22:49.730", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:traefik:traefik:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "688B9BE9-40C2-423A-8FF1-131EF920CD23", "versionEndExcluding": "2.6.1"}], "operator": "OR"}]}, {"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:oracle:communications_unified_inventory_management:7.5.0:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "0EBC7EB1-FD72-4BFC-92CC-7C8B8E462D7C"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}