CVE-2015-6744: n/a vulnerability

CVE-2015-6744: Basware Banking (Maksuliikenne) before 8.90.07.X relies on the client to enforce (1) login verification, (2...

Basware Banking (Maksuliikenne) before 8.90.07.X relies on the client to enforce (1) login verification, (2) audit trail creation, and (3) account locking, which allows remote attackers to "disrupt security-critical functions" by "dropping network traffic." NOTE: this identifier was SPLIT from CVE-2015-0942 per ADT2 and ADT3 due to different vulnerability type and different affected versions.

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

Security readout for executives and security teams

Basware Banking/Maksuliikenne versions before 8.90.07.X depended on the client application for key security checks. If attackers could interfere with network traffic, login verification, audit logging, or account locking could be disrupted. For payment operations, weakened audit and account-lock controls raise business risk even though no CVSS score is provided. Exposure appears limited to organizations running Basware Banking/Maksuliikenne versions earlier than 8.90.07.X. The provided CVE data has no CPEs or vendor/product normalization, so confirm product naming and deployed versions through asset inventory and vendor records. Treat as high priority if the affected software supports payment or banking operations. The business issue is loss of confidence in authentication, account lockout, and audit records, not just system availability. Prioritize version confirmation and vendor-supported remediation. Mitigation focus: Identify all Basware Banking/Maksuliikenne installations and exact versions.; Move off versions earlier than 8.90.07.X if vendor guidance confirms remediation there.; Ask Basware for current security advisories and supported upgrade paths..

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-6744 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.