Motorola Vulnerabilities

Timeline

The analysis of the timeline helps to identify the required approach and handling of single items and item collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Prioritizing items becomes possible.

Type

The moderation team is working with the threat intelligence team to categorize software that is affected by security vulnerabilities. This helps to illustrate the assignment of these categories to determine the most affected software types.

Product

Motorola CX211
Motorola M210
Motorola Solutions Vigilant Fixed LPR Coms Box7
Motorola CX2L Router6
Motorola MR26006

Grouping vulnerabilities by products helps to get an overview. This makes it possible to determine an homogeneous landscape or the most important hotspots in heterogeneous landscapes.

Remediation

Official Fix30
Temporary Fix0
Workaround7
Unavailable5
Not Defined75

Vendors and researchers are eager to find countermeasures to mitigate security vulnerabilities. These can be distinguished between multiple forms and levels of remediation which influence risks differently.

Exploitability

High4
Functional0
Proof-of-Concept12
Unproven0
Not Defined101

Researcher and attacker which are looking for security vulnerabilities try to exploit them for academic purposes or personal gain. The level and quality of exploitability can be distinguished to determine simplicity and strength of attacks.

Access Vector

Not Defined0
Physical8
Local25
Adjacent32
Network52

The approach a vulnerability it becomes important to use the expected access vector. This is typically via the network, local, or physically even.

Authentication

Not Defined0
High7
Low45
None65

To exploit a vulnerability a certail level of authentication might be required. Vulnerabilities without such a requirement are much more popular.

User Interaction

Not Defined0
Required5
None112

Some attack scenarios require some user interaction by a victim. This is typical for phishing, social engineering and cross site scripting attacks.

C3BM Index

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

CVSSv3 Base

≤10
≤20
≤31
≤414
≤522
≤613
≤711
≤834
≤918
≤104

The Common Vulnerability Scoring System (CVSS) is an industry standard to define the characteristics and impacts of security vulnerabilities. The base score represents the intrinsic aspects that are constant over time and across user environments. Our unique meta score merges all available scores from different sources to aggregate to the most reliable result.

CVSSv3 Temp

≤10
≤20
≤35
≤411
≤522
≤612
≤722
≤824
≤918
≤103

The Common Vulnerability Scoring System (CVSS) uses temp scores to reflect the characteristics of a vulnerability that may change over time but not across user environments. This includes reporting confidence, exploitability and remediation levels. We do also provide our unique meta score for temp scores, even though other sources rarely publish them.

VulDB

≤10
≤20
≤36
≤423
≤511
≤623
≤712
≤834
≤95
≤103

The moderation team is always defining the base vector and base score for an entry. These and all other available scores are used to generate the meta score.

NVD

≤10
≤20
≤30
≤40
≤53
≤63
≤72
≤810
≤913
≤1015

The National Vulnerability Database (NVD) is also defining CVSS vectors and scores. These are usually not complete and might differ from VulDB scores.

CNA

≤10
≤20
≤36
≤40
≤510
≤64
≤74
≤86
≤99
≤104

A CVE Numbering Authority (CNA) is responsible for assigning new CVE entries. They might also include a CVSS score. These are usually not complete and might differ from VulDB scores.

Vendor

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

Some vendors are willing to publish their own CVSS vectors and scores for vulnerabilities in their products. The coverage varies from vendor to vendor.

Research

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

There are sometimes also security researcher which provide their own CVSS vectors and scores for vulnerabilities they have found and published.

Exploit 0-day

<1k37
<2k66
<5k13
<10k0
<25k0
<50k0
<100k1
≥100k0

The moderation team is working with the threat intelligence team to determine prices for exploits. Our unique algorithm is used to identify the 0-day prices for an exploit, before it got distributed or became public. Calculated prices are aligned to prices disclosed by vulnerability broker and compared to prices we see on exploit markets.

Exploit Today

<1k106
<2k10
<5k1
<10k0
<25k0
<50k0
<100k0
≥100k0

The 0-day prices do not consider time-relevant factors. The today price does reflect price impacts like disclosure of vulnerability details, alternative exploits, availability of countermeasures. These dynamic aspects might decrease the exploit prices over time. Under certain circumstances this happens very fast.

Exploit Market Volume

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

🔴 CTI Activities

Our unique Cyber Threat Intelligence aims to determine the ongoing research of actors to anticipiate their acitivities. Observing exploit markets on the Darknet, discussions of vulnerabilities on mailinglists, and exchanges on social media makes it possible to identify planned attacks. Monitored actors and activities are classified whether they are offensive or defensive. They are also weighted as some actors are well-known for certain products and technologies. And some of their disclosures might contain more or less details about technical aspects and personal context. The world map highlights active actors in real-time.

Affected Products (71): ACE (1), ACE1000 (2), ACE1000 RTU (3), Avigilon T008 (1), Avigilon T100 (1), Avigilon T101 (1), Avigilon T103 (1), Avigilon T200 (1), Avigilon T201 (1), Avigilon T204 (1), Avigilon T205 (1), Avigilon T290 (1), C1 (5), C1 MWR03 (1), CPEi300 (2), CX2 (11), CX2L MWR04L (2), CX2L Router (6), Cable Modem (1), CableRouter (2), Device (3), Device Help App (2), Droid X2 (1), Enterprise MotoDpms Provider (1), FX9500 (2), Face Unlock App (1), Framework (1), GuideMe App (1), Interface Test Tool App (1), M2 (10), MBP853 (1), MBTS Base Radio (2), MBTS Site Controller (3), MDLC (1), MH702x (1), MM1000 (2), MOSCAD (1), MOSCAD IP Gateway (2), MOSCAD Toolbox (1), MOTORAZR (1), MR2600 (6), MR2600 Router (1), MTM5000 (4), Mobility e20 (1), PEBL U6 (3), Phone App (1), Phone Calls App (2), Phone Extension App (1), Phones (2), Q14 Mesh Router (3), RAZR (1), Ready For App (3), SBG901 (1), SBG941 (1), SBG6580 (1), SM56 Modem WDM Driver (1), SURFboard (1), SVG1202 (1), Scanner SDK (2), Services Main App (1), Setup App (1), Smartphone (1), Surfboard (2), Surfboard Sbv6120e (1), Timbuktu (2), Timbuktu Pro (1), Time Weather Widget App (1), Vanguard (1), Vigilant Fixed LPR Coms Box (7), Wr850g (1), netOctopus (1)

PublishedBaseTempVulnerabilityProdExpRemEPSSCTICVE
01/07/20254.34.3Motorola SM56 Modem WDM Driver IOCTL SmSerl64.sys Privilege EscalationHardware Driver SoftwareNot DefinedNot Defined0.000430.05CVE-2024-55414
10/08/20245.55.3Motorola CX2L Router Setting SetStationSettings command injectionRouter Operating SystemNot DefinedNot Defined0.000430.04CVE-2024-45880
08/01/20247.37.1Motorola Q14 Mesh Router API improper authenticationRouter Operating SystemNot DefinedOfficial Fix0.000430.00CVE-2022-4001
08/01/20244.03.9Motorola Q14 Mesh Router API Request resource consumptionRouter Operating SystemNot DefinedOfficial Fix0.000440.00CVE-2022-4003
08/01/20247.27.0Motorola Q14 Mesh Router API Request command injectionRouter Operating SystemNot DefinedOfficial Fix0.000490.00CVE-2022-4002
06/13/20243.53.5Motorola Solutions Vigilant Fixed LPR Coms Box cleartext storage in a file or on diskUnknownNot DefinedNot Defined0.000520.00CVE-2024-38280
06/13/20247.07.0Motorola Solutions Vigilant Fixed LPR Coms Box Maintenance Console hard-coded credentialsUnknownNot DefinedNot Defined0.001250.00CVE-2024-38281
06/13/20243.53.4Motorola Solutions Vigilant Fixed LPR Coms Box Customer Info missing encryptionUnknownNot DefinedNot Defined0.000430.03CVE-2024-38283
06/13/20243.53.4Motorola Solutions Vigilant Fixed LPR Coms Box insufficiently protected credentialsUnknownNot DefinedNot Defined0.000430.00CVE-2024-38285
06/13/20245.65.4Motorola Solutions Vigilant Fixed LPR Coms Box authentication replayUnknownNot DefinedNot Defined0.000430.04CVE-2024-38284
06/13/20248.88.5Motorola Solutions Vigilant Fixed LPR Coms Box default credentialsUnknownNot DefinedNot Defined0.000430.03CVE-2024-38282
06/13/20245.55.4Motorola Solutions Vigilant Fixed LPR Coms Box authentication bypassUnknownNot DefinedNot Defined0.000520.00CVE-2024-38279
05/03/20244.94.8Motorola Ready For App absolute path traversalUnknownNot DefinedOfficial Fix0.000430.00CVE-2023-41830
05/03/20243.13.0Motorola Ready For App path traversalUnknownNot DefinedOfficial Fix0.000440.00CVE-2023-41825
05/03/20243.13.0Motorola Phone Calls App Phone Number implicit intentUnknownNot DefinedOfficial Fix0.000430.00CVE-2023-41824
05/03/20244.94.8Motorola Phone Extension App improper export of android application componentsUnknownNot DefinedOfficial Fix0.000430.00CVE-2023-41823
05/03/20245.15.0Motorola Interface Test Tool App improper export of android application componentsUnknownNot DefinedOfficial Fix0.000430.00CVE-2023-41822
05/03/20244.14.1Motorola Setup App User Information improper export of android application componentsUnknownNot DefinedOfficial Fix0.000430.00CVE-2023-41821
05/03/20244.14.1Motorola Ready For App Bluetooth Audio Device implicit intentUnknownNot DefinedOfficial Fix0.000430.00CVE-2023-41820
05/03/20244.74.6Motorola Face Unlock App improper authorizationUnknownNot DefinedOfficial Fix0.000430.00CVE-2023-41819
05/03/20244.14.1Motorola Device Help App SD Card missing access controlUnknownNot DefinedOfficial Fix0.000430.00CVE-2023-41818
05/03/20243.13.0Motorola Phone Calls App implicit intentUnknownNot DefinedOfficial Fix0.000430.00CVE-2023-41817
05/03/20244.14.1Motorola Services Main App improper export of android application componentsUnknownNot DefinedOfficial Fix0.000430.00CVE-2023-41816
05/03/20244.94.8Motorola Phone App implicit intentUnknownNot DefinedOfficial Fix0.000430.00CVE-2023-41828
05/03/20242.82.7Motorola Framework Telephony implicit intentUnknownNot DefinedOfficial Fix0.000430.04CVE-2024-3480

92 more entries are not shown

Interested in the pricing of exploits?

See the underground prices here!