# CVE-2024-51556: Sensitive Information Disclosure Vulnerability in Wave 2.0


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 4 Nov 2024
- **Updated:** 22 Nov 2024
- **Also known as:** GHSA-6w35-x982-hj9h

## What is CVE-2024-51556?

CVE-2024-51556 is a high-severity vulnerability in Brokerage Technology Solutions Wave 2.0, published on 4 Nov 2024. 

### Official description

This vulnerability exists in the Wave 2.0 due to insufficient encryption of sensitive data received at the API response. An authenticated remote attacker could exploit this vulnerability by manipulating API input parameters through API request URL/payload leading to unauthorized access to sensitive information belonging to other users.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

## Which versions are affected by CVE-2024-51556?

It affects 2 products.


Products: 63moons Aero, 63moons Wave 2.0.

## How do I fix CVE-2024-51556?

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

## Is CVE-2024-51556 being exploited?

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

## Other vulnerabilities in Brokerage Technology Solutions Wave 2.0

- [CVE-2024-51558](https://insights.sbomify.com/CVE-2024-51558/): Brute Force Attack Vulnerability in Wave 2.0 (critical 9.3)
- [CVE-2024-51561](https://insights.sbomify.com/CVE-2024-51561/): Authentication bypass Vulnerability in Aero (critical 9.3)
- [CVE-2024-51557](https://insights.sbomify.com/CVE-2024-51557/): No Rate Limiting Vulnerability in Wave 2.0 (high 7.1)
- [CVE-2024-51559](https://insights.sbomify.com/CVE-2024-51559/): Improper Access Control Vulnerability in Wave 2.0 (high 7.1)
- [CVE-2024-51560](https://insights.sbomify.com/CVE-2024-51560/): Improper Error Handling Vulnerability in Wave 2.0 (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-51556 and fix it if it is affected.

What it is: CVE-2024-51556 is a high-severity vulnerability in Brokerage Technology Solutions Wave 2.0, published on 4 Nov 2024. 
Exploitation: There is no known exploitation of CVE-2024-51556 in the wild and no public exploit code.

Affected product: Brokerage Technology Solutions Wave 2.0. 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-2024-51556/ (Markdown: https://insights.sbomify.com/CVE-2024-51556/index.md)
```

## Sources

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

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