CVE-2022-3250: ikus060/rdiffweb · Sensitive Cookie in HTTPS Session Without 'Secure' Attribute
Affects ikus060/rdiffwebSource CVE Database V5
Not known to be exploited · CVSS 4.9 Medium : upgrade to 2.4.6 when convenient.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.4.6
CVSS:3.0/AV:A/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 21 Sep 2022
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade ikus060/rdiffweb to 2.4.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubikus060/rdiffwebpkg:github/ikus060/rdiffwebOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate this vulnerability, European organizations should: 1) Upgrade to version 2.4.6 or later of ikus060/rdiffweb where the issue is presumably fixed. 2) If upgrading is not immediately possible, implement web server or reverse proxy configurations to enforce the 'Secure' attribute on cookies set by rdiffweb, for example by using HTTP response header modifications (e.g., 'Set-Cookie' directives with 'Secure' flag). 3) Ensure strict HTTPS enforcement across all access points to rdiffweb, including redirecting all HTTP traffic to HTTPS and disabling mixed content. 4) Employ network segmentation and monitoring to limit adjacent network access to backup management interfaces. 5) Educate users about phishing and social engineering risks since user interaction is required for exploitation. 6) Regularly audit and monitor session management and access logs for suspicious activity. 7) Consider implementing additional authentication controls such as multi-factor authentication to reduce risk from session hijacking.
Description
Sensitive Cookie in HTTPS Session Without 'Secure' Attribute in GitHub repository ikus060/rdiffweb prior to 2.4.6.