FKIE_CVE-2022-30636

Vulnerability from fkie_nvd - Published: 2024-07-02 20:15 - Updated: 2026-06-17 04:43
Severity
7.5 (High) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Summary
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.
References
security@golang.orghttps://go.dev/cl/408694
security@golang.orghttps://go.dev/issue/53082
security@golang.orghttps://pkg.go.dev/vuln/GO-2024-2961
af854a3a-2127-422b-91ae-364da2661108https://go.dev/cl/408694
af854a3a-2127-422b-91ae-364da2661108https://go.dev/issue/53082
af854a3a-2127-422b-91ae-364da2661108https://pkg.go.dev/vuln/GO-2024-2961
Impacted products
Vendor Product Version
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "collectionURL": "https://pkg.go.dev",
          "defaultStatus": "unaffected",
          "packageName": "golang.org/x/crypto/acme/autocert",
          "platforms": [
            "windows"
          ],
          "product": "golang.org/x/crypto/acme/autocert",
          "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"
            }
          ],
          "vendor": "golang.org/x/crypto",
          "versions": [
            {
              "lessThan": "0.0.0-20220525230936-793ad666bf5e",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "source": "security@golang.org"
    },
    {
      "affectedData": [
        {
          "cpes": [
            "cpe:2.3:a:golang:crypto:-:*:*:*:*:*:*:*"
          ],
          "defaultStatus": "unknown",
          "product": "crypto",
          "vendor": "golang",
          "versions": [
            {
              "lessThan": "0.0.0-20220525230936-793ad666bf5e",
              "status": "affected",
              "version": "0",
              "versionType": "custom"
            }
          ]
        }
      ],
      "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"
    }
  ],
  "cveTags": [],
  "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\u00f3n de DirCache. En Windows, path.Base act\u00faa 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\u00edda tiene el sufijo +http-01, se une al directorio de cach\u00e9 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."
    }
  ],
  "id": "CVE-2022-30636",
  "lastModified": "2026-06-17T04:43:59.593",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 7.5,
          "baseSeverity": "HIGH",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "NONE",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 3.9,
        "impactScore": 3.6,
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "type": "Secondary"
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2022-30636",
          "options": [
            {
              "exploitation": "poc"
            },
            {
              "automatable": "yes"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "role": "CISA Coordinator",
          "timestamp": "2024-07-03T13:57:10.933970Z",
          "version": "2.0.3"
        }
      }
    ]
  },
  "published": "2024-07-02T20:15:05.173",
  "references": [
    {
      "source": "security@golang.org",
      "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": "af854a3a-2127-422b-91ae-364da2661108",
      "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"
    }
  ],
  "sourceIdentifier": "security@golang.org",
  "vulnStatus": "Deferred"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.