vciy

CVE-2022-3376

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

Weak Password Requirements in ikus060/rdiffweb

CVE-2022-33764 of 4 sources documented this
17

rank 17 = 0 + 13 + 0 + 4 + 0

rank@v1 · backlog

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.00749  ·  without this subject the record ranks 17

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 5.3, from NVD  ·  without this subject the record ranks 4

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 17

How much of the world it touches

NVD CPE configurations

2 products in the CPE ranges  ·  without this subject the record ranks 13

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 17

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$16,000over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$16,000 = $4.99M incident cost x 0.42806422275080447 exposure x 0.00749 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.00749EPSSNOT IN KEVas of 2026-09-20
Severity3.5 LOWreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defensefix version namedreceipt
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2022-10-07, 1438 days at 0.01, as of 2026-09-14. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Sources disagree here.

Severity score
@huntrdev3.5 LOWreceipt
NVD5.3 MEDIUMreceipt
Scoring standard
@huntrdevCVSS v3.0receipt
NVDCVSS v3.1receipt
What it costs
@huntrdevPartial confidentiality and availability lossreceipt
NVDPartial integrity lossreceipt

Both shown, dated. We don't pick winners. disagreement-rules@v1

Running ikus060/rdiffweb? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachneeds physical access · no privileges required · no user interaction · low attack complexityreceipt
ImpactPartial confidentiality and availability lossreceipt
Scored fromCVSS v3.0 · the CNA's vectorreceipt
Weakness classCWE-521 Weak Password Requirementsreceipt
Published consequencesCWE-521: Access Control: Gain Privileges or Assume Identity[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed in2.5.0a4receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, the CNA3.5 LOWreceipt
CVSS, NVD5.3 MEDIUMreceipt
Exploit probability0.00749 · top 47% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned by@huntrdevreceipt
Recorded changes30 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productikus060/rdiffwebreceipt
Published rangesikus-soft rdiffweb <= 2.4.10; ikus-soft rdiffweb 2.5.0receipt
Fixed in2.5.0a4receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

Weak Password Requirements in GitHub repository ikus060/rdiffweb prior to 2.5.0a4. receipt

NVD's analysis a second authority

severity
5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
weakness
CWE-521
affected versions
ikus-soft rdiffweb <= 2.4.10; ikus-soft rdiffweb 2.5.0

The CNA scored it 3.5 and NVD 5.3. Both are shown because both were published; we do not pick one.

check it yourself huntr.dev github.com receipt

Movement the material steps

7 Oct 20220.00885
7 Mar 20234.6e-4 · scoring model v2023.03.01
17 Mar 20250.00224 · scoring model v2025.03.14
15 Jun 20260.00672 · scoring model v2026.06.15
14 Sep 20260.00749

This score more than doubled inside 72 hours. Both observations are in the full history below.

Show all 30 observations
7 Oct 20220.00885
7 Mar 20234.6e-4
8 Mar 20230.00046
6 Sep 20230.00053
8 Nov 20230.00059
18 Mar 20240.00066
28 Apr 20240.00068
17 Dec 20240.00069
17 Mar 20250.00224
19 Mar 20250.00245
25 Mar 20250.00313
29 Mar 20250.00405
30 Mar 20250.00313
29 Apr 20250.00335
17 May 20250.00276
1 Jul 20250.00345
2 Aug 20250.00368
8 Oct 20250.0036
13 Oct 20250.00467
14 Oct 20250.00463
18 Nov 20250.00219
21 Nov 20250.00463
7 Dec 20250.00187
24 Dec 20250.00463
1 Apr 20260.00489
15 Jun 20260.00672
17 Jul 20260.00692
5 Aug 20260.00698
6 Aug 20260.00724
14 Sep 20260.00749

30 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.00749Published2022-10-06Index as of2026-09-14

Exploit probability more than doubled between 2025-11-18 and 2025-11-21 (0.00219 → 0.00463) and the record had been public for 3 years, 11 months when this index was last written.

Published 2022-10-06 receipt · Index as of 2026-09-14 derived

Siblings and hubs

Records related to this one

Its defect family

ikus060/rdiffweb

Of the 3 records in this family, this is the only one holding a stated fix version: 2.5.0a4.

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Family membership: held values

This record is one of a group, and the group's page describes all of them. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.

Browse the index from here

These are index-wide views, not findings about CVE-2022-3376.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.