CVE-2014-0336
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 the web client in Serena Dimensions CM 12.2 build 7.199.0 allows remote attackers to hijack the authentication of administrators for requests that use the user_new_master parameter to the adminconsole/ URI.
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 confidenceCSRF vulnerability in Serena Dimensions CM 12.2 adminconsole allows remote attackers to hijack administrator authentication by tricking authenticated admins into submitting malicious requests via the user_new_master parameter.
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= 12.2CVSS 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 Serena Dimensions CM installationLocate the Dimensions CM installation directory or check for processes named 'dmpool', 'dmcli', or related executables. On Windows, look in Program Files for Serena or check for the service 'Serena Dimensions CM Server'.Affected if Serena Dimensions CM is not installed on the system
-
Verify installed versionCheck the version of Serena Dimensions CM. Common methods: review installation logs, check the 'about' dialog in adminconsole, or run 'dmcli -version' if available from command line.Affected if The installed version is exactly 12.2 (other versions are not affected)
-
Confirm adminconsole accessibilityDetermine if the adminconsole web interface is accessible. Check if port 8080 or 8443 (common defaults) are open, or locate web server configuration files for the adminconsole.Affected if The adminconsole is not accessible or not configured
-
Check adminconsole form configurationAccess the adminconsole login page and examine the HTML source of forms, specifically look for forms that include the user_new_master parameter. Inspect whether anti-CSRF tokens (hidden fields with random values) are present in the form markup.Affected if The adminconsole forms lack anti-CSRF token mechanisms and the user_new_master parameter is present in accessible forms
A user is affected if Serena Dimensions CM version 12.2 is installed with the adminconsole accessible and forms lack anti-CSRF protections for the user_new_master parameter.
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 for all adminconsole forms and validate Origin/Referer headers to prevent cross-site request forgery attacks. Administrators should avoid browsing untrusted sites while logged into the admin console as a temporary workaround.
- Consultation3.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 $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0336 — 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-0336 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