# CVE-2024-28275: Information disclosure in n/a

> Attackers can intercept cleartext traffic to steal user credentials and password change requests from the 360Eyes Pro mobile application.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-6qgw-mcc6-7rxw

## What is CVE-2024-28275?

CVE-2024-28275 is a medium-severity vulnerability in n/a, published on 3 Apr 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Puwell Cloud Tech Co, Ltd 360Eyes Pro v3.9.5.16(3090516) was discovered to transmit sensitive information in cleartext. This vulnerability allows attackers to intercept and access sensitive information, including users' credentials and password change requests.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

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


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

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

## Is CVE-2024-28275 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-28275 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-28275 is a medium-severity vulnerability in n/a, published on 3 Apr 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-28275 exists.

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-2024-28275/ (Markdown: https://insights.sbomify.com/CVE-2024-28275/index.md)
```

## Sources

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

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