CVE-2015-6742
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) before 8.90.07.X uses a hardcoded password for the ANCO 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) versions before 8.90.07.X contain a hardcoded password for the ANCO account (CWE-798). Remote authenticated users who possess knowledge of this hardcoded password can bypass intended access restrictions, allowing unauthorized access to system functions or data that should be restricted.
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 Basware Banking installation and versionLocate the Basware Banking (Maksuliikenne) application and determine the installed version number. This is typically found in the application properties, about screen, or installation directory metadata.Affected if The installed version is 8.90.07 or earlier (any version <= 8.90.07).
-
Locate the ANCO account configurationSearch the Basware Banking configuration files, user directories, or database for an account named 'ANCO'. Check application configuration files, XML configs, or user management interfaces where system accounts are defined.Affected if An account with the username or identifier 'ANCO' exists in the system configuration or user database.
-
Verify hardcoded credential presenceExamine the ANCO account entry for a stored password value. Look for credentials embedded directly in configuration files, XML files, or database records rather than references to external credential stores.Affected if The ANCO account has a password value hardcoded directly in configuration files or the database, as opposed to using a secrets management system or external authentication source.
-
Confirm ANCO account is enabledCheck whether the ANCO account is active, enabled, or permitted for authentication. Review account status flags, access control lists, or authentication settings for this account.Affected if The ANCO account is enabled and capable of authenticating to the Basware Banking system.
A user is affected if their Basware Banking version is 8.90.07 or earlier and the system contains an enabled ANCO account with a hardcoded password accessible to authenticated users.
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 to version 8.90.07.X or later which presumably removes the hardcoded credential. Alternatively, if a patch is unavailable, change the hardcoded password to a strong, unique credential and implement proper secrets management. Audit all accounts for similar hardcoded credential patterns.
- Consultation4.0 h
- Implementation4.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,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6742 — 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-6742 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