# CVE-2022-46496: Weak cryptography in n/a

> The BTicino HOMETOUCH iOS app lacks SSL certificate validation, allowing attackers to intercept and read sensitive data via man-in-the-middle attacks.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 6 Feb 2023
- **Updated:** 26 Mar 2025
- **Also known as:** GHSA-2hfg-hghr-46wq

## What is CVE-2022-46496?

CVE-2022-46496 is a medium-severity vulnerability in n/a, published on 6 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

BTicino Door Entry HOMETOUCH for iOS 1.4.2 was discovered to be missing an SSL certificate.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2022-46496?

It affects 1 product.


Products: Bticino Door Entry for Hometouch.

## How do I fix CVE-2022-46496?

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

## Is CVE-2022-46496 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-46496 and fix it if it is affected.

What it is: CVE-2022-46496 is a medium-severity vulnerability in n/a, published on 6 Feb 2023. 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-2022-46496 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-2022-46496/ (Markdown: https://insights.sbomify.com/CVE-2022-46496/index.md)
```

## Sources

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

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