LiveActive security incident?Get immediate response
CVE Record

CVE-2023-23120: The use of the cyclic redundancy check (CRC) algorithm for integrity check during firmware update makes TRE...

The use of the cyclic redundancy check (CRC) algorithm for integrity check during firmware update makes TRENDnet TV-IP651WI Network Camera firmware version v1.07.01 and earlier vulnerable to firmware modification attacks. An attacker can conduct a man-in-the-middle (MITM) attack to modify the new firmware image and bypass the checksum verification.

MediumCVSS 5.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This issue affects TRENDnet TV-IP651WI network cameras running firmware v1.07.01 or earlier. The camera uses CRC checks during firmware updates, which can detect accidental corruption but not malicious tampering. A network attacker positioned between the device and update source could alter firmware and still pass the check.

Executive priority

Treat this as a targeted integrity risk for legacy network cameras, not a broad emergency. Prioritize sites where these cameras are still deployed, remotely managed, or updated across networks an attacker could intercept.

Technical view

CVE-2023-23120 is a CWE-354 firmware integrity weakness. CRC is used as the update integrity mechanism, allowing a man-in-the-middle attacker to modify a firmware image and bypass checksum verification. The CVSS 3.1 score is 5.9, with network attack vector, high complexity, no privileges, no user interaction, and high integrity impact.

Likely exposure

Exposure is limited to environments with TRENDnet TV-IP651WI cameras on firmware v1.07.01 or earlier, especially where firmware updates traverse untrusted or interceptable networks. The source bundle does not identify broader product families or confirmed internet-scale exposure.

Exploitation context

The provided sources describe a MITM firmware modification scenario, not confirmed exploitation. CISA KEV status is false in the bundle. Attack difficulty is higher because the attacker must be positioned to interfere with the firmware update path.

Researcher notes

The key weakness is reliance on CRC for firmware integrity, which is unsuitable for adversarial tampering. Provided evidence names TV-IP651WI firmware v1.07.01 and earlier. No source in the bundle confirms a vendor patch, exploit in the wild, or affected CPE metadata.

Mitigation direction

  • Check TRENDnet support for current firmware and security guidance.
  • Update affected cameras only using trusted administrative networks.
  • Avoid firmware updates over public, guest, or untrusted networks.
  • Segment cameras from business-critical systems and user workstations.
  • Restrict camera management access to authorized administrator networks.

Validation and detection

  • Inventory TRENDnet TV-IP651WI cameras and record firmware versions.
  • Flag devices running firmware v1.07.01 or earlier.
  • Review how firmware updates are downloaded and applied.
  • Check whether update traffic can cross untrusted network segments.
  • Document vendor guidance found for each deployed device version.
Prepared
Confidence
medium
Sources
4

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.

cwe · low confidence lookup

CWE-354: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-23120 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
5.9 (3.1)
Known Exploited
No
Published

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

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
5.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N2.23.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.9Medium
CVSS 3.1 vector shape for CVE-2023-23120Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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

CWE-354 · source CWE mapping

Improper Validation of Integrity Check Value

Improper Validation of Integrity Check Value represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.