CVE-2014-7874
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 HP System Management Homepage (SMH) before 3.2.3 on HP-UX B.11.23, and before 3.2.8 on HP-UX B.11.31, allows remote attackers to hijack the authentication of unspecified victims via unknown vectors.
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 HP System Management Homepage (SMH) allows remote attackers to hijack authentication of users by tricking authenticated users into submitting malicious requests to the SMH web interface. The vulnerability stems from lack of anti-CSRF tokens or proper request validation in the SMH web 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<= 3.2.2<= 3.2.7= b.11.23= b.11.31CVSS 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.
-
Verify HP System Management Homepage is installedCheck for SMH installation by looking for the product package. On HP-UX, run: swlist -l product | grep -i 'System Management Homepage' or check for the SMH installation directory (typically /opt/hp/SMH).Affected if HP System Management Homepage software is found on the system
-
Determine the installed SMH versionOn HP-UX, run: swlist -l product SMH (or check /opt/hp/SMH/bin/hpsmhversion), or access the web interface and check the version displayed on the login page or in the About section.Affected if The version returned is 3.2.2 or earlier, or 3.2.7 or earlier (specific to the HP-UX release)
-
Confirm the HP-UX operating system versionRun: uname -a or swinfo to identify if the system is running HP-UX B.11.23 or B.11.31.Affected if The system runs HP-UX B.11.23 or B.11.31 and SMH is installed at a vulnerable version
-
Check if the SMH web service is running and accessibleRun: /opt/hp/SMH/bin/hpsmhd status, or check if port 2381 (default SMH port) is listening: netstat -an | grep 2381.Affected if The SMH web service is active and the web interface is network-accessible
A system is affected if HP System Management Homepage is installed and running with version 3.2.2 or earlier on HP-UX B.11.23, or version 3.2.7 or earlier on HP-UX B.11.31, with the web interface accessible to users who could be tricked into submitting malicious requests.
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 dataUpdate HP System Management Homepage to version 3.2.3 or later (HP-UX B.11.23) or version 3.2.8 or later (HP-UX B.11.31) to resolve this vulnerability. Additionally, consider implementing SameSite cookie attributes and CSRF tokens as defense-in-depth measures.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-7874 — 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-7874 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