CyberSecBulletin
CVE-2023-45225NVD status: Modified

IP Camera CF7500: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2023-45225 is a critical-severity out-of-bounds write vulnerability in IP Camera CF7500 from Zavio, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected IP Camera CF7500 versions: version M2.1.6.05. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.62% chance of exploitation within 30 days, higher than 77% of scored CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Check which version of IP Camera CF7500 you run against the affected versions below, and install the vendor's latest release.
  2. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
ZavioIP Camera CF7500version M2.1.6.05Not stated
ZavioIP Camera CF7300version M2.1.6.05Not stated
ZavioIP Camera CF7201version M2.1.6.05Not stated
ZavioIP Camera CF7501version M2.1.6.05Not stated
ZavioIP Camera CB3211version M2.1.6.05Not stated
ZavioIP Camera CB3212version M2.1.6.05Not stated
ZavioIP Camera CB5220version M2.1.6.05Not stated
ZavioIP Camera CB6231version M2.1.6.05Not stated
ZavioIP Camera B8520version M2.1.6.05Not stated
ZavioIP Camera B8220version M2.1.6.05Not stated
ZavioIP Camera CD321version M2.1.6.05Not stated
ZavioCf7500 Firmwarem2.1.6.05Not stated
ZavioCf7300 Firmwarem2.1.6.05Not stated
ZavioCf7201 Firmwarem2.1.6.05Not stated
ZavioCf7501 Firmwarem2.1.6.05Not stated
ZavioCb3211 Firmwarem2.1.6.05Not stated
ZavioCb3212 Firmwarem2.1.6.05Not stated
ZavioCb5220 Firmwarem2.1.6.05Not stated
ZavioCb6231 Firmwarem2.1.6.05Not stated
ZavioB8520 Firmwarem2.1.6.05Not stated
ZavioB8220 Firmwarem2.1.6.05Not stated
ZavioCd321 Firmwarem2.1.6.05Not stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

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

Scoring systemScoreSeverityScored by
CVSS 3.19.8CriticalCNA (hq.dhs.gov)
CVSS 3.19.8CriticalNVD

Official description

Zavio CF7500, CF7300, CF7201, CF7501, CB3211, CB3212, CB5220, CB6231, B8520, B8220, and CD321 IP Cameras with firmware version M2.1.6.05 are vulnerable to multiple instances of stack-based overflows. While parsing certain XML elements from incoming network requests, the product does not sufficiently check or validate allocated buffer size. This may lead to remote code execution.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Out-of-bounds Write

The product writes data past the end, or before the beginning, of the intended buffer.

How developers prevent this class of flaw

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.

More Out-of-bounds Write vulnerabilities (CWE-787)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Other vulnerabilities in IP Camera CF7500

All IP Camera CF7500 vulnerabilities

Recent Out-of-bounds Write vulnerabilities

Spotted an error? Tell us.