CVE-2022-46367
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 · uneditedRumpus - FTP server Cross-site request forgery (CSRF) – Privilege escalation vulnerability that may allow privilege escalation.
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 · low confidenceRumpus FTP server contains a cross-site request forgery (CSRF) vulnerability that can be leveraged for privilege escalation. The flaw allows an attacker to trick an authenticated user into performing unintended administrative actions, potentially elevating their privileges within the application.
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<= 9.0.7.1CVSS 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 Rumpus FTP server versionLocate the installed Rumpus application and retrieve its version number, typically found in the application itself, About section, or the installer package usedAffected if The installed version is 9.0.7.1 or any earlier version (9.0.x through 9.0.7.1)
-
Confirm web interface is activeAccess the Rumpus web administration interface via browser on the configured HTTP/HTTPS port (default 8080 or 8443)Affected if The web interface is accessible and accepts authentication, as CSRF attacks target browser-based administrative actions
-
Check for anti-CSRF token usageInspect the HTML source of state-changing web pages (user management, settings, permissions) and verify whether hidden anti-CSRF tokens are included in POST/PUT request formsAffected if Forms performing administrative actions lack anti-CSRF tokens or unique request identifiers, indicating the vulnerability is present
-
Validate Origin/Referer header handlingSubmit a cross-origin test request (simulated) to observe whether the server rejects requests with mismatched Origin headers or missing Referer headers on sensitive endpointsAffected if The server accepts state-changing requests without validating Origin or Referer headers, leaving the application vulnerable to cross-site forgery
A user is affected if running Maxum Rumpus version 9.0.7.1 or earlier with the web interface enabled and without anti-CSRF protections on administrative operations.
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.
From vendor dataImplement anti-CSRF tokens on state-changing operations, validate Origin and Referer headers server-side, and apply SameSite attribute restrictions to session cookies to prevent cross-origin requests.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46367 — 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-46367 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