CVE-2014-4875
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 · uneditedCreateBossCredentials.jar in Toshiba CHEC before 6.6 build 4014 and 6.7 before build 4329 contains a hardcoded AES key, which allows attackers to discover Back Office System Server (BOSS) DB2 database credentials by leveraging knowledge of this key in conjunction with bossinfo.pro read access.
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 confidenceThe CreateBossCredentials.jar component in Toshiba CHEC versions prior to 6.6 build 4014 and 6.7 before build 4329 contains a hardcoded AES encryption key. An attacker with read access to the bossinfo.pro file can use this known AES key to decrypt stored BOSS DB2 database credentials, enabling unauthorized database access.
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.6= 6.7CVSS 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
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/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.
-
Identify if Toshiba CHEC is installedSearch for Toshiba CHEC installation directory, typically found under Program Files or a custom application path. Look for CHEC application files or registry entries indicating installation.Affected if Toshiba CHEC software is present on the system
-
Determine the installed CHEC versionCheck the version information of the Toshiba CHEC installation, typically available in the application's About section, an installer log, or version metadata file within the installation directory.Affected if Version is 6.6 with build number below 4014, OR version 6.7 with build number below 4329
-
Locate the bossinfo.pro configuration fileSearch for the file named bossinfo.pro within the Toshiba CHEC installation directory or related configuration folders. This file stores BOSS DB2 database credentials.Affected if The bossinfo.pro file exists and contains encrypted credential data
-
Check for CreateBossCredentials.jarSearch for the CreateBossCredentials.jar component within the CHEC installation directory, particularly in folders containing JAR files or build-related artifacts.Affected if The CreateBossCredentials.jar file exists in the installation
-
Verify credential exposure riskExamine the bossinfo.pro file for encrypted strings that represent DB2 credentials. If an attacker with file read access can obtain this file, the hardcoded AES key in CreateBossCredentials.jar could decrypt these credentials.Affected if Encrypted BOSS DB2 credentials exist in bossinfo.pro and the version is vulnerable as determined in step 2
A user is affected if Toshiba CHEC is installed with version 6.6 before build 4014 or version 6.7 before build 4329, and the bossinfo.pro file containing encrypted BOSS DB2 credentials is present on the system.
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 Toshiba CHEC to version 6.6 build 4014 or later, or 6.7 build 4329 or later. After patching, rotate all BOSS DB2 database credentials that may have been exposed.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-4875 — 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-4875 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