{"id":"CVE-2021-3882","aliases":["EUVD-2021-27114","GHSA-q34c-v76q-8jx6","UBUNTU-CVE-2021-3882","USN-7647-1"],"status":"published","title":"Sensitive Cookie in HTTPS Session Without 'Secure' Attribute in ledgersmb/ledgersmb","description":"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.","severity":{"version":"3.0","score":5.9,"vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-10","score":0.01134,"percentile":0.66745,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-311","CWE-614"],"published":"2021-10-14T08:20:11Z","modified":"2026-10-20T10:54:52Z","fixes":[{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"ledgersmb","fixed_in":["1.6.9+ds-1ubuntu0.1+esm1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"ledgersmb","fixed_in":["1.6.33+ds-1ubuntu0.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"ledgersmb","fixed_in":["1.6.33+ds-2.1ubuntu0.1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"ledgersmb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.6.9+ds-1ubuntu0.1+esm1"}]}],"versions":["1.6.9+ds-1","1.6.9+ds-1ubuntu0.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"ledgersmb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.6.33+ds-1ubuntu0.1"}]}],"versions":["1.6.9+ds-2.1","1.6.33+ds-1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"ledgersmb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.6.33+ds-2.1ubuntu0.1"}]}],"versions":["1.6.33+ds-2.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"ledgersmb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.3.46-1ubuntu0.1~esm1"}]}],"versions":["1.3.46-1"],"bundled":5},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"ledgersmb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.4.42+ds-1ubuntu0.1~esm1"}]}],"versions":["1.4.41+ds-1","1.4.42+ds-1"],"bundled":5},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"ledgersmb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.6.9+ds-1ubuntu0.1+esm1"}]}],"versions":["1.6.9+ds-1","1.6.9+ds-1ubuntu0.1"],"bundled":5},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"ledgersmb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.6.33+ds-1ubuntu0.1"}]}],"versions":["1.6.9+ds-2.1","1.6.33+ds-1"],"bundled":5},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"ledgersmb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.6.33+ds-2.1ubuntu0.1"}]}],"versions":["1.6.33+ds-2.1"],"bundled":5}],"products":[{"vendor":"ledgersmb","product":"ledgersmb"},{"vendor":"ledgersmb","product":"ledgersmb/ledgersmb"}],"references":[{"url":"https://huntr.dev/bounties/7061d97a-98a5-495a-8ba0-3a4c66091e9d","tags":["x_refsource_CONFIRM","x_transferred","Exploit","Third Party Advisory","evidence","report"]},{"url":"https://github.com/ledgersmb/ledgersmb/commit/c242f5a2abf4b99b0da205473cbba034f306bfe2","tags":["x_refsource_MISC","x_transferred","Patch","Third Party Advisory","fix","report"]},{"url":"https://ledgersmb.org/cve-2021-3882-sensitive-non-secure-cookie","tags":["x_refsource_MISC","x_transferred","Broken Link","web","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-3882"},{"url":"https://github.com/advisories/GHSA-q34c-v76q-8jx6"},{"url":"https://ubuntu.com/security/CVE-2021-3882","tags":["report"]},{"url":"https://huntr.dev/bounties/7061d97a-98a5-495a-8ba0-3a4c66091e9d/","tags":["report"]},{"url":"https://ledgersmb.org/content/security-advisory-cve-2021-3882-non-secure-session-cookie","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-3882","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-7647-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2021-3693","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2021-3694","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2021-3731","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-23831","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2021-3882","title":"Sensitive Cookie in HTTPS Session Without 'Secure' Attribute in ledgersmb/ledgersmb","description":"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.","status":"published","published":"2021-10-14T08:20:11Z","modified":"2024-08-03T17:09:09.825Z","cvss":[{"version":"3.0","score":5.9,"vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N","level":"medium","assessor":"cna"}],"cwes":["CWE-614"],"updated_at":"2026-11-02T14:33:03.671751Z"}],"euvd":[{"id":"EUVD-2021-27114","description":"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.","status":"published","published":"2021-10-14T08:20:11Z","modified":"2024-08-03T17:09:09Z","cvss":[{"version":"3.0","score":5.9,"vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N","level":"medium"}],"updated_at":"2026-11-03T03:25:11.376657Z"}],"ghsa":[{"id":"GHSA-q34c-v76q-8jx6","title":"LedgerSMB does not set the 'Secure' attribute on the session authorization cookie when the client...","description":"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.","status":"published","published":"2022-05-24T19:17:38Z","modified":"2024-02-05T18:31:36Z","cvss":[{"version":"3.1","score":6.8,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N","level":"medium"}],"cwes":["CWE-311","CWE-614"],"updated_at":"2026-11-02T14:55:33.593991Z"}],"nvd":[{"id":"CVE-2021-3882","description":"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.","status":"published","published":"2021-10-14T09:15:08.427Z","modified":"2026-06-17T04:05:56.423Z","cvss":[{"version":"3.1","score":6.8,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N","level":"medium","assessor":"primary"},{"version":"3.0","score":5.9,"vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N","level":"medium","assessor":"secondary"},{"version":"2.0","score":4,"vector":"AV:N/AC:H/Au:N/C:P/I:P/A:N","level":"medium","assessor":"primary"}],"cwes":["CWE-614","CWE-311"],"updated_at":"2026-11-02T14:06:59.689345Z"}],"osv":[{"id":"CVE-2021-3882","description":"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.","status":"published","published":"2021-10-14T09:15:08.427Z","modified":"2026-10-20T10:54:52.479748064Z","cvss":[{"version":"3.1","score":6.8,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N","level":"medium"}],"updated_at":"2026-11-02T15:44:20.843843Z"},{"id":"UBUNTU-CVE-2021-3882","description":"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.","status":"published","published":"2021-10-14T09:15:00Z","modified":"2026-02-04T04:22:46.341451Z","cvss":[{"version":"3.0","score":5.9,"vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N","level":"medium"},{"version":"3.1","score":6.8,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N","level":"medium"}],"updated_at":"2026-11-02T15:54:28.526929Z"},{"id":"USN-7647-1","title":"ledgersmb vulnerabilities","description":"It was discovered that LedgerSMB did not check the origin of HTML\nfragments. An attacker could possibly use this issue to send a\nmaliciously crafted URL to the server and obtain sensitive\ninformation, or execute arbitrary code. This issue only affected\nUbuntu 22.04 LTS, Ubuntu 24.04 LTS, and Ubuntu 25.04.\n(CVE-2021-3693)\n\nIt was discovered that LedgerSMB did not properly encode HTML\nerror messages. An attacker could possibly use this issue to send\na maliciously crafted URL to the server and obtain sensitive\ninformation, or execute arbitrary code. This issue only affected\nUbuntu 18.04 LTS. (CVE-2021-3694)\n\nIt was discovered that LedgerSMB did not guard against discrete\nlink redirections. An attacker could possibly use this issue to\nobtain sensitive information. This issue only affected Ubuntu\n16.04 LTS and Ubuntu 18.04 LTS. (CVE-2021-3731)\n\nIt was discovered that LedgerSMB did not properly set the 'Secure'\nattribute during HTTPS sessions. If a user were tricked into using\nan unencrypted connection, an attacker could possibly use this\nissue to obtain sensitive information. This issue only affected\nUbuntu 20.04 LTS, Ubuntu 22.04 LTS, Ubuntu 24.04 LTS, and Ubuntu\n25.04. (CVE-2021-3882)\n\nIt was discovered that LedgerSMB could create admin accounts via\na URL. If an admin were tricked into clicking a maliciously\ncrafted URL, an attacker could possibly use this issue to\nachieve privilege escalation. This issue only affected Ubuntu 20.04\nLTS, Ubuntu 22.04 LTS, Ubuntu 24.04 LTS, and Ubuntu 25.04.\n(CVE-2024-23831)","status":"published","published":"2025-07-17T14:39:24Z","modified":"2026-06-25T13:32:30.663791012Z","updated_at":"2026-11-02T16:58:21.91885Z"}]}}