dbcve.org
Ecns280 Td FirmwareOperating system · Huawei

CVE-2021-40007

MEDIUM · 6.5 CVSS v3.1 Published 2021-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
There is an information leak vulnerability in eCNS280_TD V100R005C10SPC650. The vulnerability is caused by improper log output management. An attacker with the ability to access the log file of device may lead to information disclosure.

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 · moderate confidence

This is an information disclosure vulnerability in Huawei eCNS280_TD V100R005C10SPC650 where improper log output management causes sensitive information to be written to log files. An attacker with access to the device log files can read this exposed information, potentially including credentials, session data, or system details.

MitigationReview and sanitize all log output to remove sensitive information, implement proper access controls on log files to restrict unauthorized access, and apply any vendor-supplied patches for improved log management.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ecns280 Td FirmwareOperating system
Affected:= v100r005c10spc650

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 firmware version
    Access the device management interface or check system information to confirm the installed firmware version is Huawei eCNS280_TD V100R005C10SPC650
    Affected if The installed version matches exactly V100R005C10SPC650
  2. Locate log files on the system
    Check common log directories on the device (typically /var/log, /log, or device-specific log paths) to identify where the system writes operational logs
    Affected if Log files exist on the system and the firmware version is affected
  3. Examine log contents for sensitive data
    Search through the log files for patterns indicating sensitive information such as passwords, usernames, session tokens, API keys, or system configuration details that should not be exposed
    Affected if Log files contain any credentials, session identifiers, or sensitive configuration data that should not be logged
  4. Verify access controls on log files
    Check file permissions and ownership on identified log files to determine if unauthorized users could read them
    Affected if Log files are readable by users other than administrators or the application owner

A user is affected if the device runs firmware version V100R005C10SPC650 and log files contain sensitive information that should not have been written or are accessible to unauthorized users

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Review and sanitize all log output to remove sensitive information, implement proper access controls on log files to restrict unauthorized access, and apply any vendor-supplied patches for improved log management.

Recommended fix Moderate confidence

Obtain the fixed firmware version from Huawei (contact Huawei technical support for the specific patched release)

  1. Contact Huawei technical support to obtain the security patch or firmware update for eCNS280_TD V100R005C10SPC650
  2. Request the specific security advisory or patch for CVE-2021-40007 from Huawei
  3. Apply the provided firmware update following Huawei's standard upgrade procedures
  4. After patching, verify that log output no longer contains sensitive information
  5. Review and restrict access to log files to authorized personnel only

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ecns280 Td Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-40007 — 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-2021-40007 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