# CVE-2020-26230: Deanonymization of COVID-19 positive users of Radar COVID - **Severity:** High 7.4 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Fix available:** No - **Published:** 13 Nov 2020 - **Updated:** 4 Aug 2024 - **Also known as:** GHSA-w7jx-37x3-w2jx ## What is CVE-2020-26230? CVE-2020-26230 is a high-severity vulnerability in RadarCOVID radar-covid-backend-dp3t-server, published on 13 Nov 2020. ### Official description Radar COVID is the official COVID-19 exposure notification app for Spain. In affected versions of Radar COVID, identification and de-anonymization of COVID-19 positive users that upload Radar COVID TEKs to the Radar COVID server is possible. This vulnerability enables the identification and de-anonymization of COVID-19 positive users when using Radar COVID. The vulnerability is caused by the fact that Radar COVID connections to the server (uploading of TEKs to the backend) are only made by COVID-19 positives. Therefore, any on-path observer with the ability to monitor traffic between the app and the server can identify which users had a positive test. Such an adversary can be the mobile network operator (MNO) if the connection is done through a mobile network, the Internet Service Provider (ISP) if the connection is done through the Internet (e.g., a home network), a VPN provider used by the user, the local network operator in the case of enterprise networks, or any eavesdropper with access to the same network (WiFi or Ethernet) as the user as could be the case of public WiFi hotspots deployed at shopping centers, airports, hotels, and coffee shops. The attacker may also de-anonymize the user. For this additional stage to succeed, the adversary needs to correlate Radar COVID traffic to other identifiable information from the victim. This could be achieved by associating the connection to a contract with the name of the victim or by associating Radar COVID traffic to other user-generated flows containing identifiers in the clear (e.g., HTTP cookies or other mobile flows sending unique identifiers like the IMEI or the AAID without encryption). The former can be executed, for instance, by the Internet Service Provider or the MNO. The latter can be executed by any on-path adversary, such as the network provider or even the cloud provider that hosts more than one service accessed by the victim. The farther the adversary is either from the victim (the client) or the end-point (the server), the less likely it may be that the adversary has access to re-identification information. The vulnerability has been mitigated with the injection of dummy traffic from the application to the backend. Dummy traffic is generated by all users independently of whether they are COVID-19 positive or not. The issue was fixed in iOS in version 1.0.8 (uniform distribution), 1.1.0 (exponential distribution), Android in version 1.0.7 (uniform distribution), 1.1.0 (exponential distribution), Backend in version 1.1.2-RELEASE. For more information see the referenced GitHub Security Advisory. Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2020-26230? It affects 2 products. Products: Radarcovid Radar-Covid-Backend-Dp3t-Server, Radarcovid Radarcovid. ## How do I fix CVE-2020-26230? No fix has been published for CVE-2020-26230 yet. Limit exposure of the affected software until one is available. ## Is CVE-2020-26230 being exploited? There is no known exploitation of CVE-2020-26230 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-26230 and fix it if it is affected. What it is: CVE-2020-26230 is a high-severity vulnerability in RadarCOVID radar-covid-backend-dp3t-server, published on 13 Nov 2020. Exploitation: There is no known exploitation of CVE-2020-26230 in the wild and no public exploit code. Affected product: RadarCOVID radar-covid-backend-dp3t-server. 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-2020-26230/ (Markdown: https://insights.sbomify.com/CVE-2020-26230/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-26230 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-26230 - OSV: https://osv.dev/vulnerability/CVE-2020-26230 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-26230/ Summaries are generated and may contain mistakes; the official description above is the record.