Security readout for executives and security teams
Plain-English summary
Certain UCWeb UC browser versions reportedly send browsing activity over unencrypted HTTP, allowing someone on the network path to see visited URLs. This is primarily a privacy and confidentiality issue, not evidence of device takeover.
Executive priority
Treat as a moderate privacy exposure. Prioritize environments handling sensitive browsing activity, executives, regulated users, and unmanaged mobile fleets.
Technical view
CVE-2020-36473 describes cleartext HTTP use in UCWeb UC 12.12.3.1219 through 12.12.3.1226. A man-in-the-middle observer could discover visited URLs. The source bundle provides no CVSS score, CWE mapping, platform detail, patch version, or vendor advisory.
Likely exposure
Exposure appears limited to users running UCWeb UC versions 12.12.3.1219 through 12.12.3.1226. The bundle does not identify operating systems, package sources, or CPEs.
Exploitation context
The CVE is not listed as CISA KEV in the bundle. Exploitation requires observation or interception on the network path. No source here confirms active exploitation.
Researcher notes
Evidence is sparse. The CVE description is clear about URL disclosure via HTTP, but lacks affected platform, CVSS, fix status, and detailed protocol behavior. Avoid expanding scope beyond the named versions.
Mitigation direction
- Inventory UCWeb UC browser installations and versions.
- Check vendor or app-store guidance for fixed versions.
- Remove or replace affected versions where URL privacy matters.
- Avoid using affected versions on untrusted networks.
Validation and detection
- Confirm whether UCWeb UC is installed in managed endpoints.
- Verify installed versions against 12.12.3.1219 through 12.12.3.1226.
- Review network telemetry for cleartext HTTP browsing from affected clients.
- Document any compensating controls for unmanaged mobile users.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2020-36473 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://medium.com/%40ciph3r/why-you-should-not-use-uc-browser-54558916d020CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
