Sensitive Cookie in HTTPS Session Without 'Secure' Attribute in ledgersmb/ledgersmb

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.

N/A

HTTPS会话中未设置’Secure’属性的敏感Cookie

LedgerSMB 安全漏洞

LedgerSMB是一个免费的基于网络的复式记账系统，具有报价、订购、发票、项目、考勤卡、库存管理、运输等功能。 LedgerSMB存在安全漏洞，该漏洞源于当客户端使用HTTPS且LedgerSMB服务器位于反向代理后面时，LedgerSMB没有在会话授权cookie上设置Secure属性。通过欺骗用户使用未加密的连接(HTTP)，攻击者可利用该漏洞通过捕获网络流量来获取身份验证数据。LedgerSMB 1.8及更新版本从基本身份验证切换到使用加密cookie身份验证。虽然攻击者不能访问cookie内部的

N/A

N/A