CVE-2015-6744
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network without logging in. Limited direct impact.
- Exploit odds
- 1.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 1.1% in the next 30 days (EPSS).
- Severity: 4.3 MEDIUM (CVSS).
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 1.1% · EPSS, next 30 days
- Record status
- Modified
Affected
- Basware Banking ≤ 8.90.07
Attack profile CVSS 2.0 · 4.3
- Attack vector
- Network
- Complexity
- Medium
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
Raw vector
AV:N/AC:M/Au:N/C:N/I:N/A:P
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2015-6744.md and follow it. Check whether this project is affected by CVE-2015-6744. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
