CVE-2015-6747
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 · uneditedBasware Banking (Maksuliikenne) 8.90.07.X does not properly prevent access to private keys, which allows remote attackers to spoof communications with banks via unspecified vectors. NOTE: this identifier was SPLIT from CVE-2015-0942 per ADT2 due to different vulnerability types. NOTE: this vulnerability exists because of an incorrect fix for CVE-2015-6746.
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 confidenceBasware Banking (Maksuliikenne) version 8.90.07.X contains a private key exposure vulnerability where the software fails to properly protect cryptographic private keys. This allows unauthorized actors to access these keys, potentially enabling them to impersonate the legitimate system and spoof communications with banks. The flaw exists as a regression from an incomplete fix for CVE-2015-6746.
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<= 8.90.07CVSS 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.
-
Check installed Basware Banking versionUse the software's built-in version information feature or check the application binary metadata to determine the exact version numberAffected if The installed version is 8.90.07 or any version within the 8.90.07.X family (e.g., 8.90.07.1, 8.90.07.2)
-
Identify private key storage locationsSearch the Basware installation directory and associated data directories for files commonly containing private keys, such as .key, .pem, .p12, .pfx, or keystore filesAffected if Private key files exist in locations accessible to the Basware application user or other system users
-
Examine file permissions on private key filesUse operating system commands (such as ls -l on Linux or icacls on Windows) to inspect access control lists on any identified private key filesAffected if Private key files grant read access to user accounts other than the dedicated service account or administrator
-
Verify private key accessibilityAttempt to read private key files using a non-privileged test account or by examining whether the files are world-readableAffected if Non-administrator or non-service accounts can read the private key files
-
Check for regression of CVE-2015-6746Review any recent patches or updates applied to address CVE-2015-6746 and verify whether the private key protection mechanism was re-introduced or bypassedAffected if The environment was previously patched for CVE-2015-6746 but private keys remain exposed
A user is affected if they are running Basware Banking version 8.90.07 or earlier AND private key files are accessible to unauthorized accounts due to improper file permission settings.
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 dataRemediate by reviewing and properly securing private key storage mechanisms, ensuring keys are never accessible to unauthorized processes or users. Implement proper key protection such as hardware security modules (HSM) or OS-level file permissions, and verify the fix does not reintroduce the underlying issue from CVE-2015-6746.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6747 — 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-2015-6747 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