mirror of
https://github.com/fkie-cad/nvd-json-data-feeds.git
synced 2025-05-28 01:02:25 +00:00
60 lines
3.7 KiB
JSON
60 lines
3.7 KiB
JSON
{
|
|
"id": "CVE-2023-48703",
|
|
"sourceIdentifier": "security-advisories@github.com",
|
|
"published": "2024-03-06T20:15:47.343",
|
|
"lastModified": "2024-03-06T21:42:48.053",
|
|
"vulnStatus": "Awaiting Analysis",
|
|
"cveTags": [],
|
|
"descriptions": [
|
|
{
|
|
"lang": "en",
|
|
"value": "RobotsAndPencils go-saml, a SAML client library written in Go, contains an authentication bypass vulnerability in all known versions. This is due to how the `xmlsec1` command line tool is called internally to verify the signature of SAML assertions. When `xmlsec1` is used without defining the enabled key data, the origin of the public key for the signature verification is, unfortunately, not restricted. That means an attacker can sign the SAML assertions themselves and provide the required public key (e.g. an RSA key) directly embedded in the SAML token. Projects still using RobotsAndPencils/go-saml should move to another SAML library or alternatively remove support for SAML from their projects. The vulnerability can likely temporarily be fixed by forking the go-saml project and adding the command line argument `--enabled-key-data` and specifying a value such as `x509` or `raw-x509-cert` when calling the `xmlsec1` binary in the verify function. Please note that this workaround must be carefully tested before it can be used."
|
|
},
|
|
{
|
|
"lang": "es",
|
|
"value": "RobotsAndPencils go-saml, una librer\u00eda cliente SAML escrita en Go, contiene una vulnerabilidad de omisi\u00f3n de autenticaci\u00f3n en todas las versiones conocidas. Esto se debe a c\u00f3mo se llama internamente a la herramienta de l\u00ednea de comando `xmlsec1` para verificar la firma de las aserciones SAML. Cuando se utiliza `xmlsec1` sin definir los datos de la clave habilitada, desafortunadamente el origen de la clave p\u00fablica para la verificaci\u00f3n de la firma no est\u00e1 restringido. Eso significa que un atacante puede firmar las afirmaciones SAML por s\u00ed mismo y proporcionar la clave p\u00fablica requerida (por ejemplo, una clave RSA) directamente integrada en el token SAML. Los proyectos que todav\u00eda usan RobotsAndPencils/go-saml deben trasladarse a otra librer\u00eda SAML o, alternativamente, eliminar la compatibilidad con SAML de sus proyectos. Es probable que la vulnerabilidad pueda solucionarse temporalmente bifurcando el proyecto go-saml y agregando el argumento de l\u00ednea de comando `--enabled-key-data` y especificando un valor como `x509` o `raw-x509-cert` al llamar al ` xmlsec1` binario en la funci\u00f3n de verificaci\u00f3n. Tenga en cuenta que esta workaround se debe probar cuidadosamente antes de poder utilizarla."
|
|
}
|
|
],
|
|
"metrics": {
|
|
"cvssMetricV31": [
|
|
{
|
|
"source": "security-advisories@github.com",
|
|
"type": "Secondary",
|
|
"cvssData": {
|
|
"version": "3.1",
|
|
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
|
|
"attackVector": "NETWORK",
|
|
"attackComplexity": "LOW",
|
|
"privilegesRequired": "NONE",
|
|
"userInteraction": "NONE",
|
|
"scope": "UNCHANGED",
|
|
"confidentialityImpact": "NONE",
|
|
"integrityImpact": "HIGH",
|
|
"availabilityImpact": "NONE",
|
|
"baseScore": 7.5,
|
|
"baseSeverity": "HIGH"
|
|
},
|
|
"exploitabilityScore": 3.9,
|
|
"impactScore": 3.6
|
|
}
|
|
]
|
|
},
|
|
"weaknesses": [
|
|
{
|
|
"source": "security-advisories@github.com",
|
|
"type": "Secondary",
|
|
"description": [
|
|
{
|
|
"lang": "en",
|
|
"value": "CWE-287"
|
|
}
|
|
]
|
|
}
|
|
],
|
|
"references": [
|
|
{
|
|
"url": "https://securitylab.github.com/advisories/GHSL-2023-121_go-saml__archived_/",
|
|
"source": "security-advisories@github.com"
|
|
}
|
|
]
|
|
} |