CVE-2022-29238

{"id": "CVE-2022-29238", "metrics": {"cvssMetricV2": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"version": "2.0", "baseScore": 4.0, "accessVector": "NETWORK", "vectorString": "AV:N/AC:L/Au:S/C:P/I:N/A:N", "authentication": "SINGLE", "integrityImpact": "NONE", "accessComplexity": "LOW", "availabilityImpact": "NONE", "confidentialityImpact": "PARTIAL"}, "acInsufInfo": false, "impactScore": 2.9, "baseSeverity": "MEDIUM", "obtainAllPrivilege": false, "exploitabilityScore": 8.0, "obtainUserPrivilege": false, "obtainOtherPrivilege": false, "userInteractionRequired": false}], "cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 4.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "LOW"}, "impactScore": 1.4, "exploitabilityScore": 2.8}, {"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 4.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "LOW"}, "impactScore": 1.4, "exploitabilityScore": 2.8}]}, "published": "2022-06-14T18:15:08.150", "references": [{"url": "https://github.com/jupyter/notebook/security/advisories/GHSA-v7vq-3x77-87vg", "tags": ["Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/jupyter/notebook/security/advisories/GHSA-v7vq-3x77-87vg", "tags": ["Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-425"}]}], "descriptions": [{"lang": "en", "value": "Jupyter Notebook is a web-based notebook environment for interactive computing. Prior to version 6.4.12, authenticated requests to the notebook server with `ContentsManager.allow_hidden = False` only prevented listing the contents of hidden directories, not accessing individual hidden files or files in hidden directories (i.e. hidden files were 'hidden' but not 'inaccessible'). This could lead to notebook configurations allowing authenticated access to files that may reasonably be expected to be disallowed. Because fully authenticated requests are required, this is of relatively low impact. But if a server's root directory contains sensitive files whose only protection from the server is being hidden (e.g. `~/.ssh` while serving $HOME), then any authenticated requests could access files if their names are guessable. Such contexts also necessarily have full access to the server and therefore execution permissions, which also generally grants access to all the same files. So this does not generally result in any privilege escalation or increase in information access, only an additional, unintended means by which the files could be accessed. Version 6.4.12 contains a patch for this issue. There are currently no known workarounds."}, {"lang": "es", "value": "Jupyter Notebook es un entorno de cuadernos basado en la web para la computaci\u00f3n interactiva. En versiones anteriores a 6.4.12, las peticiones autenticadas al servidor del cuaderno con \"ContentsManager.allow_hidden = False\" s\u00f3lo imped\u00edan listar el contenido de los directorios ocultos, no acceder a archivos individuales ocultos o a los archivos de directorios ocultos (es decir, los archivos ocultos estaban \"ocultos\" pero no \"inaccesibles\"). Esto podr\u00eda conllevar a que las configuraciones de los ordenadores port\u00e1tiles permitieran el acceso autenticado a archivos que razonablemente fueran esperados a que no estuvieran permitidos. Dado que son requeridas peticiones totalmente autenticadas, esto presenta un impacto relativamente bajo. Pero si el directorio root de un servidor contiene archivos confidenciales cuya \u00fanica protecci\u00f3n frente al servidor es estar oculto (por ejemplo, \"~/.ssh\" mientras sirve $HOME), entonces cualquier petici\u00f3n autenticada podr\u00eda acceder a los archivos si sus nombres son adivinables. Tales contextos tambi\u00e9n presentan necesariamente acceso completo al servidor y, por lo tanto, permisos de ejecuci\u00f3n, lo que generalmente tambi\u00e9n otorga acceso a todos los mismos archivos. Por lo tanto, esto no suele resultar en una escalada de privilegios o a un aumento del acceso a la informaci\u00f3n, sino a un medio adicional e involuntario por el que podr\u00eda accederse a los archivos. La versi\u00f3n 6.4.12 contiene un parche para este problema. Actualmente no son conocidas mitigaciones para este problema"}], "lastModified": "2024-11-21T06:58:46.993", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:jupyter:notebook:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "73055684-47E0-4131-AEE6-8736AB80A3B3", "versionEndExcluding": "6.4.12"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}