LiveActive security incident?Get immediate response
CVE Record

CVE-2019-20472: An issue was discovered on One2Track 2019-12-08 devices.

An issue was discovered on One2Track 2019-12-08 devices. Any SIM card used with the device cannot have a PIN configured. If a PIN is configured, the device simply produces a "Remove PIN and restart!" message, and cannot be used. This makes it easier for an attacker to use the SIM card by stealing the device.

MediumCVSS 6.2Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Some One2Track devices cannot operate when their SIM card has a PIN enabled. Because users must remove the SIM PIN for the device to work, a stolen device or SIM may be easier to misuse. The source bundle does not identify a patch, affected model list, or active exploitation.

Executive priority

Handle as a moderate physical-security and asset-management risk. It is not documented as remotely exploitable or actively exploited, but it weakens a basic SIM protection control for deployed tracking devices. Prioritize inventory confirmation and vendor guidance over emergency response.

Technical view

CVE-2019-20472 describes One2Track 2019-12-08 devices rejecting SIM cards with PIN protection, showing a remove-PIN-and-restart message. The CVSS vector is local, low complexity, no privileges, no user interaction, with high availability impact. The record does not provide CWE mapping, CPEs, or specific version ranges.

Likely exposure

Exposure is likely limited to organizations or individuals still using One2Track tracking devices matching the 2019-12-08 description. The bundle does not provide exact models, firmware versions, or CPE identifiers, so asset confirmation requires inventory review against vendor or device records.

Exploitation context

No CISA KEV listing or cited active exploitation evidence is provided. Abuse appears to require local physical possession or theft of the device or SIM. The practical risk is reduced SIM protection and possible device unavailability when a PIN is configured.

Researcher notes

The public record is sparse: affected vendor/product fields are n/a, no CWE is assigned, and no patch is named. The core issue is a design or operational constraint around SIM PIN handling rather than a conventional remote software flaw.

Mitigation direction

  • Check One2Track guidance for affected models, firmware status, and replacement options.
  • Do not treat SIM PIN as a usable control for these devices.
  • For lost devices, suspend the associated SIM through the carrier promptly.
  • Use carrier account controls to limit misuse where available.
  • Review whether these devices remain appropriate for sensitive tracking use.

Validation and detection

  • Inventory One2Track devices and identify any matching the 2019-12-08 description.
  • Confirm whether devices require SIM PIN removal to operate.
  • Check vendor or supplier records for model and firmware details.
  • Review carrier logs for unusual activity tied to device SIMs.
  • Document compensating controls for stolen-device and SIM misuse scenarios.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CVE-2019-20472 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.2CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H2.53.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.2Medium
CVSS 3.1 vector shape for CVE-2019-20472Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.