CVE-2014-2974
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 · uneditedCross-site request forgery (CSRF) vulnerability in php/user_account.php in Silver Peak VX through 6.2.4 allows remote attackers to hijack the authentication of administrators for requests that create administrative accounts.
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 · high confidenceCross-site request forgery (CSRF) vulnerability in php/user_account.php in Silver Peak VX through version 6.2.4 allows remote attackers to create administrative accounts by tricking authenticated administrators into submitting malicious requests. The attack exploits the lack of anti-CSRF tokens or origin validation in the administrative user creation functionality.
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<= 6.2.4= 6.2.2.0_47968CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 Silver Peak VX versionAccess the admin UI System > Maintenance > Diagnostics or use CLI command 'show version' to retrieve the firmware versionAffected if The installed version is 6.2.4 or any version prior to 6.2.4 (including 6.2.2.0_47968)
-
Locate the vulnerable PHP scriptAccess the web interface and navigate to or request php/user_account.php - this is the script referenced in the CVEAffected if The file php/user_account.php exists and is accessible via the web interface
-
Verify lack of CSRF protection in admin user creationLog into the admin interface, navigate to user account creation, and inspect the HTML forms for the presence of anti-CSRF tokens or unique request identifiersAffected if The user creation forms in php/user_account.php lack anti-CSRF tokens and do not validate Origin or Referer headers
-
Confirm admin interface exposureDetermine if the Silver Peak admin web interface is accessible from untrusted networks or the internet rather than only from trusted management networksAffected if The admin interface is exposed to untrusted users who could trick authenticated admins into visiting malicious pages
-
Audit for unauthorized administrative accountsReview system logs and user account lists in the admin UI under User Management or System > Administration for newly created administrator accounts not created by authorized personnelAffected if Unknown or unexpected administrator accounts exist in the system
You are affected if your Silver Peak VX version is 6.2.4 or earlier AND the php/user_account.php script is accessible with no CSRF protection tokens in the admin user creation functionality.
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 dataUpgrade to Silver Peak VX version 6.2.4 or later which should contain CSRF protection. If patching is not immediately possible, implement temporary mitigations such as validating the Origin/Referer headers server-side and monitoring for unauthorized administrative account creation.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2974 — 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-2014-2974 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