LiveActive security incident?Get immediate response
CVE Record

CVE-2022-3274: Cross-Site Request Forgery (CSRF) on user's settings in GitHub repository ikus060/rdiffweb prior to 2.4.6. in ikus060/rdiffweb

Cross-Site Request Forgery (CSRF) in GitHub repository ikus060/rdiffweb prior to 2.4.7.

HighCVSS 7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-3274 is a high-severity CSRF issue in ikus060/rdiffweb user settings. A successful attack could cause an authenticated user to make unintended settings changes, with the CVSS vector indicating high confidentiality and availability impact. The source bundle does not show active exploitation.

Executive priority

Prioritize remediation for any rdiffweb deployment that protects backup or recovery workflows. The issue is not reported as actively exploited here, but the potential confidentiality and availability impact makes delayed patching risky for operational resilience.

Technical view

The vulnerability is CWE-352 Cross-Site Request Forgery in rdiffweb before the fixed versions cited in the record. The bundle is inconsistent: the title says prior to 2.4.6, while the description says prior to 2.4.7. CVSS 3.0 score is 7.0 with PR:L and UI:R.

Likely exposure

Exposure is likely limited to organizations running ikus060/rdiffweb versions before the fixed release cited by the CVE record, especially where authenticated users manage settings through a browser. Confirm installed versions because the bundled version statements conflict.

Exploitation context

No KEV listing or cited source in the bundle confirms active exploitation. Based on CVSS, exploitation requires user interaction and low privileges, meaning risk depends on authenticated user access and whether attackers can induce browser requests.

Researcher notes

The strongest evidence is the CVE record, huntr report reference, and GitHub fixing commit. Version data needs care because the provided title and description disagree. Avoid claiming exploitation in the wild without additional evidence.

Mitigation direction

  • Inventory all rdiffweb deployments and record exact versions.
  • Upgrade affected rdiffweb instances per vendor guidance and the fixing commit.
  • Treat pre-2.4.7 builds as suspect until vendor guidance confirms otherwise.
  • Restrict rdiffweb access to trusted networks and authenticated administrators.
  • Review user settings for unexpected changes after remediation.

Validation and detection

  • Confirm whether any rdiffweb instance is below the fixed version cited by the CVE.
  • Review the referenced GitHub commit to identify the security control changed.
  • Check application logs for suspicious settings changes around user sessions.
  • Verify CSRF protections exist on user settings forms after upgrade.
  • Document the title and description version discrepancy in the vulnerability ticket.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-3274 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:A/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7CVSS 3.0HighCVSS:3.0/AV:A/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:H1.55.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

7High
CVSS 3.0 vector shape for CVE-2022-3274Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:A/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ikus060ikus060/rdiffwebunspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.