CVE-2015-6745: n/a vulnerability

CVE-2015-6745: Basware Banking (Maksuliikenne) 8.90.07.X relies on the client to enforce account locking, which allows loc...

Basware Banking (Maksuliikenne) 8.90.07.X relies on the client to enforce account locking, which allows local users to bypass that security mechanism by deleting the entry from the locking table. NOTE: this identifier was SPLIT from CVE-2015-0942 per ADT2 and ADT3 due to different vulnerability type and different affected versions. NOTE: this vulnerability exists because of an incorrect fix for CVE-2015-6744.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 6, 2024, 07:29 UTC (UTC+00:00)

Security readout for executives and security teams

CVE-2015-6745 affects Basware Banking, also known as Maksuliikenne, 8.90.07.X. The reported issue is that account locking was enforced by the client, allowing a local user to bypass the lock mechanism by removing the relevant lock entry. This weakens access-control protections in a banking/payment context, but the sources provide no CVSS score or confirmed active exploitation. Exposure appears limited to environments running Basware Banking/Maksuliikenne 8.90.07.X where local users can interact with the client or its lock-state storage. Internet exposure is not indicated. Organizations using this legacy banking software should treat exposure as operationally sensitive because account-locking controls protect payment-system access. Prioritize if this software is still used for banking or payment workflows. The issue undermines lockout controls but appears to require local access, so urgency depends on whether legacy Basware clients remain deployed and who can access them. Mitigation focus: Inventory Basware Banking/Maksuliikenne installations and identify any 8.90.07.X versions.; Check Basware or national advisory guidance for supported upgrades or fixes.; Restrict local access to systems running the banking client..

Prepared: Jun 13, 2026, 22:03 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2015-6745 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Aug 31, 2015, 14:08 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
https://www.viestintavirasto.fi/en/cybersecurity/vulnerabilities/2015/haavoittuvuus-2015-018.htmlCVE reference · x_refsource_MISC

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.