CVE-2021-3882

{"id": "CVE-2021-3882", "metrics": {"cvssMetricV2": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"version": "2.0", "baseScore": 4.0, "accessVector": "NETWORK", "vectorString": "AV:N/AC:H/Au:N/C:P/I:P/A:N", "authentication": "NONE", "integrityImpact": "PARTIAL", "accessComplexity": "HIGH", "availabilityImpact": "NONE", "confidentialityImpact": "PARTIAL"}, "acInsufInfo": false, "impactScore": 4.9, "baseSeverity": "MEDIUM", "obtainAllPrivilege": false, "exploitabilityScore": 4.9, "obtainUserPrivilege": false, "obtainOtherPrivilege": false, "userInteractionRequired": true}], "cvssMetricV30": [{"type": "Secondary", "source": "security@huntr.dev", "cvssData": {"scope": "UNCHANGED", "version": "3.0", "baseScore": 5.9, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "REQUIRED", "attackComplexity": "HIGH", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 4.2, "exploitabilityScore": 1.6}], "cvssMetricV31": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 6.8, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "REQUIRED", "attackComplexity": "HIGH", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.2, "exploitabilityScore": 1.6}]}, "published": "2021-10-14T09:15:08.427", "references": [{"url": "https://github.com/ledgersmb/ledgersmb/commit/c242f5a2abf4b99b0da205473cbba034f306bfe2", "tags": ["Patch", "Third Party Advisory"], "source": "security@huntr.dev"}, {"url": "https://huntr.dev/bounties/7061d97a-98a5-495a-8ba0-3a4c66091e9d", "tags": ["Exploit", "Third Party Advisory"], "source": "security@huntr.dev"}, {"url": "https://ledgersmb.org/cve-2021-3882-sensitive-non-secure-cookie", "tags": ["Broken Link"], "source": "security@huntr.dev"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "CWE-311"}]}, {"type": "Secondary", "source": "security@huntr.dev", "description": [{"lang": "en", "value": "CWE-614"}]}], "descriptions": [{"lang": "en", "value": "LedgerSMB does not set the 'Secure' attribute on the session authorization cookie when the client uses HTTPS and the LedgerSMB server is behind a reverse proxy. By tricking a user to use an unencrypted connection (HTTP), an attacker may be able to obtain the authentication data by capturing network traffic. LedgerSMB 1.8 and newer switched from Basic authentication to using cookie authentication with encrypted cookies. Although an attacker can't access the information inside the cookie, nor the password of the user, possession of the cookie is enough to access the application as the user from which the cookie has been obtained. In order for the attacker to obtain the cookie, first of all the server must be configured to respond to unencrypted requests, the attacker must be suitably positioned to eavesdrop on the network traffic between the client and the server *and* the user must be tricked into using unencrypted HTTP traffic. Proper audit control and separation of duties limit Integrity impact of the attack vector. Users of LedgerSMB 1.8 are urged to upgrade to known-fixed versions. Users of LedgerSMB 1.7 or 1.9 are unaffected by this vulnerability and don't need to take action. As a workaround, users may configure their Apache or Nginx reverse proxy to add the Secure attribute at the network boundary instead of relying on LedgerSMB. For Apache, please refer to the 'Header always edit' configuration command in the mod_headers module. For Nginx, please refer to the 'proxy_cookie_flags' configuration command."}, {"lang": "es", "value": "LedgerSMB no establece el atributo \"Secure\" en la cookie de autorizaci\u00f3n de sesi\u00f3n cuando el cliente usa HTTPS y el servidor LedgerSMB est\u00e1 detr\u00e1s de un proxy inverso. Al enga\u00f1ar a un usuario para que use una conexi\u00f3n no cifrada (HTTP), un atacante puede ser capaz de obtener los datos de autenticaci\u00f3n capturando el tr\u00e1fico de la red. LedgerSMB versiones 1.8 y m\u00e1s recientes, cambiaron de la autenticaci\u00f3n B\u00e1sica a un uso de la autenticaci\u00f3n con cookies cifradas. Aunque un atacante no puede acceder a la informaci\u00f3n dentro de la cookie, ni a la contrase\u00f1a del usuario, la posesi\u00f3n de la cookie es suficiente para acceder a la aplicaci\u00f3n como el usuario del que se ha obtenido la cookie. Para que el atacante obtenga la cookie, en primer lugar el servidor debe estar configurado para responder a peticiones no cifradas, el atacante debe estar convenientemente posicionado para espiar el tr\u00e1fico de red entre el cliente y el servidor *y* el usuario debe ser enga\u00f1ado para usar tr\u00e1fico HTTP no cifrado. Un control de auditor\u00eda apropiado y la separaci\u00f3n de funciones limitan el impacto de la integridad del vector de ataque. Se insta a usuarios de LedgerSMB 1.8 a que se actualicen a las versiones corregidas conocidas. Los usuarios de LedgerSMB versiones 1.7 o 1.9 no est\u00e1n afectados por esta vulnerabilidad y no necesitan tomar medidas. Como soluci\u00f3n, los usuarios pueden configurar su proxy inverso Apache o Nginx para a\u00f1adir el atributo Secure en el l\u00edmite de la red en lugar de confiar en LedgerSMB. Para Apache, consulte el comando de configuraci\u00f3n \"Header always edit\" en el m\u00f3dulo mod_headers. Para Nginx, consulte el comando de configuraci\u00f3n \"proxy_cookie_flags\""}], "lastModified": "2024-02-05T17:14:03.927", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:ledgersmb:ledgersmb:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "FE34EF1E-8A98-462C-8D5F-B095F845B9F6", "versionEndExcluding": "1.8.22", "versionStartIncluding": "1.8.0"}], "operator": "OR"}]}], "sourceIdentifier": "security@huntr.dev"}