CVE-2022-30636
httpTokenCacheKey uses path.Base to extract the expected HTTP-01 token value to lookup in the DirCache implementation. On Windows, path.Base acts differently to filepath.Base, since Windows uses a different path separator (\ vs. /), allowing a user to provide a relative path, i.e. .well-known/acme-challenge/..\..\asd becomes ..\..\asd. The extracted path is then suffixed with +http-01, joined with the cache directory, and opened. Since the controlled path is suffixed with +http-01 before opening, the impact of this is significantly limited, since it only allows reading arbitrary files on the system if and only if they have this suffix.
CVSS
- Versión: 3.1
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Puntuación base: 7.5
Probabilidad de explotación (EPSS)
- Probabilidad de explotación en los próximos 30 días: 0.64%
- Percentil entre todas las CVEs puntuadas: 49
- Fecha de la puntuación: 7/10/2026
EPSS (Exploit Prediction Scoring System, de FIRST) estima la probabilidad de que una vulnerabilidad sea explotada en 30 días. Complementa a CVSS (impacto) y a CISA KEV (explotación confirmada).
Tecnologías afectadas (1)
⚠ Inferidas por IA a partir de la descripción — NVD aún no ha analizado esta CVE; no son CPE verificados.
Referencias
JSON original (NVD)
Mostrar
{
"id": "CVE-2022-30636",
"cveTags": [],
"metrics": {
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2022-30636",
"role": "CISA Coordinator",
"options": [
{
"exploitation": "poc"
},
{
"automatable": "yes"
},
{
"technicalImpact": "partial"
}
],
"version": "2.0.3",
"timestamp": "2024-07-03T13:57:10.933970Z"
}
}
],
"cvssMetricV31": [
{
"type": "Secondary",
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"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:H/I:N/A:N",
"integrityImpact": "NONE",
"userInteraction": "NONE",
"attackComplexity": "LOW",
"availabilityImpact": "NONE",
"privilegesRequired": "NONE",
"confidentialityImpact": "HIGH"
},
"impactScore": 3.6,
"exploitabilityScore": 3.9
}
]
},
"affected": [
{
"source": "security@golang.org",
"affectedData": [
{
"vendor": "golang.org/x/crypto",
"product": "golang.org/x/crypto/acme/autocert",
"versions": [
{
"status": "affected",
"version": "0",
"lessThan": "0.0.0-20220525230936-793ad666bf5e",
"versionType": "semver"
}
],
"platforms": [
"windows"
],
"packageName": "golang.org/x/crypto/acme/autocert",
"collectionURL": "https://pkg.go.dev",
"defaultStatus": "unaffected",
"programRoutines": [
{
"name": "DirCache.Get"
},
{
"name": "DirCache.Put"
},
{
"name": "DirCache.Delete"
},
{
"name": "HostWhitelist"
},
{
"name": "Manager.GetCertificate"
},
{
"name": "Manager.Listener"
},
{
"name": "NewListener"
},
{
"name": "listener.Accept"
},
{
"name": "listener.Close"
}
]
}
]
},
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"affectedData": [
{
"cpes": [
"cpe:2.3:a:golang:crypto:-:*:*:*:*:*:*:*"
],
"vendor": "golang",
"product": "crypto",
"versions": [
{
"status": "affected",
"version": "0",
"lessThan": "0.0.0-20220525230936-793ad666bf5e",
"versionType": "custom"
}
],
"defaultStatus": "unknown"
}
]
}
],
"published": "2024-07-02T20:15:05.173",
"references": [
{
"url": "https://go.dev/cl/408694",
"source": "security@golang.org"
},
{
"url": "https://go.dev/issue/53082",
"source": "security@golang.org"
},
{
"url": "https://pkg.go.dev/vuln/GO-2024-2961",
"source": "security@golang.org"
},
{
"url": "https://go.dev/cl/408694",
"source": "af854a3a-2127-422b-91ae-364da2661108"
},
{
"url": "https://go.dev/issue/53082",
"source": "af854a3a-2127-422b-91ae-364da2661108"
},
{
"url": "https://pkg.go.dev/vuln/GO-2024-2961",
"source": "af854a3a-2127-422b-91ae-364da2661108"
}
],
"vulnStatus": "Deferred",
"descriptions": [
{
"lang": "en",
"value": "httpTokenCacheKey uses path.Base to extract the expected HTTP-01 token value to lookup in the DirCache implementation. On Windows, path.Base acts differently to filepath.Base, since Windows uses a different path separator (\\ vs. /), allowing a user to provide a relative path, i.e. .well-known/acme-challenge/..\\..\\asd becomes ..\\..\\asd. The extracted path is then suffixed with +http-01, joined with the cache directory, and opened. Since the controlled path is suffixed with +http-01 before opening, the impact of this is significantly limited, since it only allows reading arbitrary files on the system if and only if they have this suffix."
},
{
"lang": "es",
"value": "httpTokenCacheKey usa path.Base para extraer el valor del token HTTP-01 esperado para buscarlo en la implementación de DirCache. En Windows, path.Base actúa de manera diferente a filepath.Base, ya que Windows usa un separador de ruta diferente (\\ vs. /), lo que permite al usuario proporcionar una ruta relativa, es decir, .well-known/acme-challenge/..\\. .\\asd se convierte en ..\\..\\asd. Luego, la ruta extraída tiene el sufijo +http-01, se une al directorio de caché y se abre. Dado que la ruta controlada tiene el sufijo +http-01 antes de abrirse, el impacto de esto es significativamente limitado, ya que solo permite leer archivos arbitrarios en el sistema si y solo si tienen este sufijo."
}
],
"lastModified": "2026-06-17T04:43:59.593",
"sourceIdentifier": "security@golang.org"
}