# CVE-2015-6747: Information disclosure in n/a

> Remote attackers can access private keys to spoof bank communications due to improper access controls in Basware Banking software.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-5rh4-w9mq-q4mq

## What is CVE-2015-6747?

CVE-2015-6747 is a medium-severity vulnerability in n/a, published on 31 Aug 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Basware Banking (Maksuliikenne) 8.90.07.X does not properly prevent access to private keys, which allows remote attackers to spoof communications with banks via unspecified vectors.  NOTE: this identifier was SPLIT from CVE-2015-0942 per ADT2 due to different vulnerability types.  NOTE: this vulnerability exists because of an incorrect fix for CVE-2015-6746.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2015-6747?

It affects 1 product.


Products: Basware Banking.

## How do I fix CVE-2015-6747?

No fix has been published for CVE-2015-6747 yet. Limit exposure of the affected software until one is available.

## Is CVE-2015-6747 being exploited?

There is no known exploitation of CVE-2015-6747 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2015-6742](https://insights.sbomify.com/CVE-2015-6742/): Hardcoded credentials in n/a (medium 6.5)
- [CVE-2015-6743](https://insights.sbomify.com/CVE-2015-6743/): Hardcoded credentials in n/a (medium 6.5)
- [CVE-2015-0943](https://insights.sbomify.com/CVE-2015-0943/): Weak cryptography in n/a (medium 5.8)
- [CVE-2015-6745](https://insights.sbomify.com/CVE-2015-6745/): Security feature bypass in n/a (medium 4.6)
- [CVE-2015-6744](https://insights.sbomify.com/CVE-2015-6744/): Security feature bypass in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-6747 and fix it if it is affected.

What it is: CVE-2015-6747 is a medium-severity vulnerability in n/a, published on 31 Aug 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-6747 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2015-6747/ (Markdown: https://insights.sbomify.com/CVE-2015-6747/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2015-6747
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-6747
- OSV: https://osv.dev/vulnerability/CVE-2015-6747

---
From sbomify Insights: https://insights.sbomify.com/CVE-2015-6747/
Summaries are generated and may contain mistakes; the official description above is the record.