dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-35341

HIGH · 7.5 CVSS v3.1 Published 2024-05-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Certain Anpviz products allow unauthenticated users to download the running configuration of the device via a HTTP GET request to /ConfigFile.ini or /config.xml URIs. This configuration file contains usernames and encrypted passwords (encrypted with a hardcoded key common to all devices). This affects IPC-D250, IPC-D260, IPC-B850, IPC-D850, IPC-D350, IPC-D3150, IPC-D4250, IPC-D380, IPC-D880, IPC-D280, IPC-D3180, MC800N, YM500L, YM800N_N2, YMF50B, YM800SV2, YM500L8, and YM200E10 firmware v3.2.2.2 and lower and possibly more vendors/models of IP camera.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An unauthenticated file disclosure vulnerability in Anpviz IP camera firmware v3.2.2.2 and lower allows remote attackers to retrieve the device configuration file via HTTP GET requests to /ConfigFile.ini or /config.xml. The configuration contains usernames and passwords encrypted with a hardcoded key common to all affected devices, enabling credential theft and potential device compromise.

MitigationUpdate firmware to a patched version if available; if no patch exists, implement network segmentation and firewall rules to restrict access to the device management interface, and change any default credentials as defense-in-depth.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device as an Anpviz IP camera
    Access the device's web interface or check the device's administrative pages for the model name and manufacturer information. Look for 'Anpviz' branding or model numbers known to be from this vendor.
    Affected if The device is confirmed to be an Anpviz IP camera or NVR product.
  2. Check the firmware version
    Log into the device's web interface and navigate to System or Settings > Firmware/Version information. Compare the installed firmware version to v3.2.2.2 - versions 3.2.2.2 and lower are affected.
    Affected if The firmware version is 3.2.2.2 or lower, or the version cannot be determined but the device is Anpviz.
  3. Test for unauthenticated access to /ConfigFile.ini
    Using a web browser or curl command, send an HTTP GET request to http://<device_ip>/ConfigFile.ini without providing any authentication credentials.
    Affected if The request returns the configuration file content without requiring login.
  4. Test for unauthenticated access to /config.xml
    Using a web browser or curl command, send an HTTP GET request to http://<device_ip>/config.xml without providing any authentication credentials.
    Affected if The request returns the configuration file content without requiring login.
  5. Verify the config contains credentials
    Examine the retrieved configuration file and look for user account entries containing username fields and encrypted password fields.
    Affected if The configuration file contains username and password fields, indicating the flaw exposes credential data.

A user is affected if the device is an Anpviz IP camera running firmware v3.2.2.2 or lower AND the /ConfigFile.ini or /config.xml endpoints are accessible without authentication, returning a configuration file with credential data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update firmware to a patched version if available; if no patch exists, implement network segmentation and firewall rules to restrict access to the device management interface, and change any default credentials as defense-in-depth.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-35341 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-35341 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data