CVE-2015-0943: n/a vulnerability

CVE-2015-0943: Basware Banking (Maksuliikenne) before 9.10.0.0 does not encrypt communication between the client and the b...

Basware Banking (Maksuliikenne) before 9.10.0.0 does not encrypt communication between the client and the backend server, which allows man-in-the-middle attackers to obtain encryption keys, user credentials, and other sensitive information by sniffing the network or modify this traffic by inserting packets into the client-server data stream.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 6, 2024, 04:26 UTC (UTC+00:00)

Security readout for executives and security teams

Basware Banking (Maksuliikenne) before 9.10.0.0 reportedly sent sensitive client-server banking traffic without encryption. Someone positioned on the network could read credentials, encryption keys, or other sensitive data, and could alter traffic. This is most urgent for organizations still running legacy Basware Banking systems. Exposure is likely limited to organizations using Basware Banking/Maksuliikenne versions earlier than 9.10.0.0. Risk is higher where client-server traffic crosses shared, flat, or untrusted networks. The bundle does not provide CPEs or a complete affected-version matrix. Prioritize if Basware Banking remains in use. The business concern is direct exposure of banking credentials and sensitive transaction-related data on the network. If the product is retired or upgraded beyond 9.10.0.0, residual urgency is lower but should be documented. Mitigation focus: Upgrade Basware Banking/Maksuliikenne to 9.10.0.0 or later where applicable.; Check Basware and national advisory guidance for supported remediation details.; Restrict client-server traffic to trusted, segmented network 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-0943 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.