CVE-2015-6743
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 uses a hardcoded password for an unspecified account, which allows remote authenticated users to bypass intended access restrictions by leveraging knowledge of this password. NOTE: this identifier was SPLIT from CVE-2015-0942 per ADT2 and ADT3 due to different vulnerability types and different affected versions.
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 hardcoded password embedded in the software for an unspecified account. Remote authenticated users who discover this password can bypass intended access restrictions, effectively creating an authentication bypass backdoor.
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
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/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 installed Basware Banking versionLocate the Maksuliikenne application in the system and check its version information, typically found in the application metadata, installer details, or about dialog. Compare the version number against the affected range: <= 8.90.07Affected if The installed version is 8.90.07 or any earlier version (8.x.x or lower)
-
Locate hardcoded credential strings in application filesSearch the Basware Banking installation directory and configuration files for suspicious hardcoded password strings. Use grep or similar tools to search for patterns like 'password=', 'pwd=', or Base64-encoded credential strings embedded in configuration files, scripts, or executable resourcesAffected if A hardcoded password is found in any configuration file, script, or embedded resource within the application installation directory
-
Audit application user accountsReview the list of configured user accounts within Basware Banking, looking for any unspecified, undocumented, or unexpected accounts that should not exist according to system documentationAffected if An undocumented or unknown user account exists in the system that is not authorized by your organization's identity management policy
-
Test for authentication bypass using the backdoor accountIf a hardcoded password is discovered or an undocumented account is found, attempt to authenticate using those credentials from a remote location to verify the backdoor is functionalAffected if Authentication succeeds using credentials that were not assigned through proper onboarding procedures or are not documented in the authorized user directory
A user is affected if their Basware Banking installation is version 8.90.07 or lower AND contains a hardcoded password or undocumented account that allows unauthorized access.
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 dataRemove the hardcoded password from the codebase and implement proper credential management such as environment variables, a secure credential vault, or externalized configuration. Audit all accounts and their permissions to ensure the unspecified account does not provide unintended elevated access.
- Consultation3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6743 — 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-6743 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