CVE-2021-3882
First published: Thu Oct 14 2021(Updated: )
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.
Credit: security@huntr.dev security@huntr.dev
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Ledgersmb Ledgersmb | =1.8.0 | |
| Ledgersmb Ledgersmb | >=1.8.0<1.8.22 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the vulnerability ID of this LedgerSMB vulnerability?
The vulnerability ID for this LedgerSMB vulnerability is CVE-2021-3882.
What is the severity of the LedgerSMB vulnerability (CVE-2021-3882)?
The severity of the LedgerSMB vulnerability (CVE-2021-3882) is medium with a CVSS score of 6.8.
How does the LedgerSMB vulnerability (CVE-2021-3882) affect the software?
The LedgerSMB vulnerability (CVE-2021-3882) affects LedgerSMB version 1.8.0.
What is the impact of the LedgerSMB vulnerability (CVE-2021-3882)?
The impact of the LedgerSMB vulnerability (CVE-2021-3882) is that an attacker may be able to obtain authentication data by capturing network traffic.
How can I fix the LedgerSMB vulnerability (CVE-2021-3882)?
To fix the LedgerSMB vulnerability (CVE-2021-3882), it is recommended to set the 'Secure' attribute on the session authorization cookie when the client uses HTTPS and the LedgerSMB server is behind a reverse proxy.
- collector/nvd-index
- agent/references
- agent/severity
- agent/weakness
- agent/author
- agent/type
- agent/event
- agent/description
- agent/first-publish-date
- agent/softwarecombine
- agent/remedy
- agent/last-modified-date
- agent/tags
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- vendor/ledgersmb
- canonical/ledgersmb ledgersmb
- version/ledgersmb ledgersmb/1.8.0