CVE-2022-34367
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDell EMC Data Protection Central versions 19.1, 19.2, 19.3, 19.4, 19.5, 19.6, contain(s) a Cross-Site Request Forgery Vulnerability. A(n) remote unauthenticated attacker could potentially exploit this vulnerability, leading to processing of unintended server operations.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceDell EMC Data Protection Central versions 19.1-19.6 contain a Cross-Site Request Forgery (CSRF) vulnerability. This allows a remote unauthenticated attacker to trick authenticated users into unknowingly submitting malicious requests to the server, potentially leading to unauthorized server operations being processed.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 19.1, < 19.7CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Dell EMC Data Protection Central versionAccess the product's About or Version information page in the administrative console, or run the product's version check command if available in the management interfaceAffected if The reported version is 19.1, 19.2, 19.3, 19.4, 19.5, or 19.6 (any version >= 19.1 but < 19.7)
-
Confirm user authentication is required for exploitationVerify that the Data Protection Central administrative interface requires user authentication to access state-changing functionsAffected if The interface allows authenticated sessions and the attacker can trick a logged-in user into submitting requests
-
Inspect session cookie configurationLog into the Data Protection Central interface and use browser developer tools or a proxy to examine the Set-Cookie headers for session cookies. Look for the SameSite attributeAffected if Session cookies lack the SameSite=Strict or SameSite=Lax attribute, or the SameSite attribute is missing entirely
-
Check for anti-CSRF token implementationExamine the application's form submissions and AJAX requests through a proxy. Look for any token parameters in POST requests that change state (configuration changes, user management, etc.)Affected if State-changing requests do not include anti-CSRF tokens or unique request identifiers, or the server does not validate Origin/Referer headers
You are affected if the installed Data Protection Central version is 19.1 through 19.6 and the application lacks anti-CSRF protections such as tokens and SameSite cookie attributes.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped19.7
Implement anti-CSRF tokens for state-changing operations, validate Origin/Referer headers server-side, and configure SameSite attributes on session cookies to prevent cross-site request forgery attacks.
19.7
- 1. Identify the current installed version of Dell EMC Data Protection Central
- 2. Schedule a maintenance window for the upgrade
- 3. Back up current configuration and data according to Dell backup procedures
- 4. Download Dell EMC Data Protection Central version 19.7 or later from Dell support portal
- 5. Follow Dell's documented upgrade procedure to install version 19.7
- 6. Verify the upgrade was successful by checking the installed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34367 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-34367 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data