# GSD-2022-1000065: Various phone carriers are blocking Apples Private Relay when users connect via cellular data.

> Mobile carriers block Apple Private Relay on cellular networks, potentially undermining user privacy and network management capabilities.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jan 2022

## What is GSD-2022-1000065?

GSD-2022-1000065 is a vulnerability, published on 10 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Various phone carriers are blocking Apples Private Relay when users connect via cellular data. 

 Many of the carriers claim "The letter said that Private Relay cuts off networks and servers from accessing “vital network data and metadata” and will have “significant consequences in terms of undermining European digital sovereignty”. They say it will also impact “operator’s ability to efficiently manage telecommunication networks”." Please note that the majority of these carriers are not blocking VPN products which provide similar functionality.

## Which versions are affected by GSD-2022-1000065?


## How do I fix GSD-2022-1000065?

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

## Is GSD-2022-1000065 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for GSD-2022-1000065 and fix it if it is affected.

What it is: GSD-2022-1000065 is a vulnerability, published on 10 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GSD-2022-1000065 in the wild and no public exploit code.

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/GSD-2022-1000065/ (Markdown: https://insights.sbomify.com/GSD-2022-1000065/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GSD-2022-1000065

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