CVE-2014-2622
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 · uneditedUnspecified vulnerability in HP Intelligent Management Center (iMC) before 7.0 E02020P03 and Branch Intelligent Management System (BIMS) before 7.0 E0201P02 allows remote authenticated users to obtain sensitive information or modify data via unknown vectors, aka ZDI-CAN-2312.
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 confidenceHP Intelligent Management Center (iMC) and Branch Intelligent Management System (BIMS) contain an unspecified vulnerability (ZDI-CAN-2312) that allows remote authenticated users to obtain sensitive information or modify data via unknown vectors. Affected versions are iMC before 7.0 E02020P03 and BIMS before 7.0 E0201P02.
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= 7.0= 7.0CVSS 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
- Authentication
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- None
AV:N/AC:L/Au:S/C:C/I:C/A:N
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.
-
Check if HP Intelligent Management Center (iMC) is installedLocate the iMC installation directory or check Windows services for 'HP iMC' or 'imc' services. The typical install path is C:\Program Files\HP\iMC or /opt/hp/imc on Linux.Affected if iMC is installed on the system
-
Determine the installed iMC versionCheck the version file in the iMC installation directory, typically found in server\conf\version.xml or by running the iMC client and viewing About information. The version format appears as 7.0 followed by a patch identifier like E0201.Affected if iMC version is 7.0 with a patch level before E02020P03 (for example, E0201, E0202, E02010P01, etc.)
-
Check if HP Branch Intelligent Management System (BIMS) is installedLocate the BIMS installation directory or check for the BIMS service. Typical paths include C:\Program Files\HP\BIMS or /opt/hp/bims.Affected if BIMS is installed on the system
-
Determine the installed BIMS versionCheck the version file in the BIMS installation directory, typically in conf\version.xml or view the version through the BIMS client interface.Affected if BIMS version is 7.0 with a patch level before E0201P02 (for example, base 7.0, E0201, E02010P01, etc.)
A system is affected if HP iMC version 7.0 is earlier than E02020P03, or if HP BIMS version 7.0 is earlier than E0201P02.
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 HP iMC to version 7.0 E02020P03 or later, and BIMS to version 7.0 E0201P02 or later, as the official patch addresses this vulnerability.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2622 — 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-2622 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