CVE-2024-56901
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 · uneditedA Cross-Site Request Forgery (CSRF) vulnerability in Geovision GV-ASWeb application with the version 6.1.1.0 or less that allows attackers to arbitrarily create Administrator accounts via a crafted GET request method. This vulnerability is used in chain with CVE-2024-56903 for a successful CSRF attack.
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 confidenceA CSRF vulnerability in Geovision GV-ASWeb (version 6.1.1.0 and below) allows remote attackers to create arbitrary Administrator accounts by tricking authenticated users into submitting crafted GET requests. This flaw is exploited in conjunction with CVE-2024-56903 to execute a successful CSRF attack chain.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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 Geovision GV-ASWeb installationAccess the web interface and locate the version information, typically found in the login page footer, about section, or system info pageAffected if The product is Geovision GV-ASWeb and version displays as 6.1.1.0 or lower
-
Verify the current installed versionCheck the GV-ASWeb admin interface for the exact version number under System Settings or About, and compare it to the affected range of 6.1.1.0 and belowAffected if Version is 6.1.1.0 or any version below (e.g., 6.1.0.0, 6.0.x, etc.)
-
Confirm account creation functionality existsLog into the GV-ASWeb admin panel and navigate to User Management or Account Settings to verify the presence of an account/user creation featureAffected if The account creation interface is present and accessible to the authenticated administrator
-
Test for missing CSRF protection on account creationInspect the HTTP requests when creating a new user via the admin interface; check if the request includes anti-CSRF tokens in headers or form parameters, and verify the server validates the Origin or Referer headerAffected if The account creation request lacks anti-CSRF tokens and does not validate Origin or Referer headers, allowing crafted GET requests to succeed
You are affected if Geovision GV-ASWeb version 6.1.1.0 or below is running and the account creation endpoint lacks anti-CSRF token validation.
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 and origin/referer validation for all state-changing operations, particularly account creation endpoints; update to the latest patched version if available.
- Consultation4.0 h
- Implementation8.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 $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-56901 — 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-2024-56901 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