CVE Tools
Track your stack

CVE-2022-3326

Weak Password Requirements in ikus060/rdiffweb

No known exploitation. EPSS puts it in the 53rd percentile. Fixed in 2.4.9.

CVSS 3.14.3MediumEPSS percentile53rd0.7% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix2.4.9Upgrade to this build

Published Updated Sources: CVE.org, NVD, GitHub

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • Ikus060/rdiffwebAffected: ≥ unspecified, < 2.4.9Upgrade to: 2.4.9Stated by: CVE record
  • PyPI rdiffwebAffected: < 2.4.9Upgrade to: 2.4.9Stated by: GitHub advisory
  • Ikus-soft RdiffwebAffected: < 2.4.9Upgrade to: 2.4.9Stated by: NVD

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Check the installed rdiffweb version; you are affected if it is 2.4.8 or earlier.
  2. Upgrade rdiffweb to version 2.4.9 or later.
  3. Review rdiffweb user passwords and replace any weak passwords after upgrading.
pip install --upgrade "rdiffweb>=2.4.9"
Vendor advisory Usually a quick update

What it is

From the CVE record

Weak Password Requirements in GitHub repository ikus060/rdiffweb prior to 2.4.9.

In plain language

Written by AI from the record

If you use rdiffweb 2.4.8 or earlier, update it: weak password rules can make unauthorized account access easier.

CVE-2022-3326 is a CWE-521 weak-password-requirements flaw in rdiffweb prior to 2.4.9, allowing authenticated low-privilege users to make limited integrity-impacting changes.

If you're affected

  • Weaker account protection
  • Unauthorized account changes
  • Limited system changes

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS53rd
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.7% chance of exploitation activity in the next 30 days, which ranks it in the 53rd percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

5 events over 785 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. Publishedweakness classified, att&ck mapped

Affected products

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Scored 4.3 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required LowRequires basic user-level privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality NoneNo confidentiality impact
  • Integrity LowData modification is possible but limited in scope or consequence
  • Availability NoneNo availability impact

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

And 2 more references. See all after sign-in

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Ikus060/rdiffweb, not every advisory.