dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2024-29150

HIGH · 8.8 CVSS v3.1 Published 2024-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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
An issue was discovered in Alcatel-Lucent ALE NOE deskphones through 86x8_NOE-R300.1.40.12.4180 and SIP deskphones through 86x8_SIP-R200.1.01.10.728. Because of improper privilege management, an authenticated attacker is able to create symlinks to sensitive and protected data in locations that are used for debugging files. Given that the process of gathering debug logs is carried out with root privileges, any file referenced in the symlink is consequently written to the debug archive, thereby granting accessibility to the attacker.

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

Authenticated attackers can create symlinks in debug log directories on Alcatel-Lucent ALE deskphones (NOE and SIP variants). Since the debug log collection process runs with root privileges, any symlinked file—whether inside or outside the device's filesystem—gets copied into the debug archive, allowing the attacker to exfiltrate sensitive data they normally couldn't access.

MitigationApply vendor-supplied firmware updates (NOE-R300.1.40.12.418+ and SIP-R200.1.01.10.728+) that address the improper privilege management. Until patches are available, disable remote debugging features and restrict authenticated access to trusted personnel only.

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

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

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 device model and firmware version
    Access the deskphone web interface or admin panel and locate the firmware version information. For NOE variants, check under Settings > Device Info or similar. For SIP variants, check under Administration or System status. Compare the displayed version number against the fixed releases (NOE-R300.1.40.12.418+ and SIP-R200.1.01.10.728+).
    Affected if The device is an ALE deskphone (NOE or SIP variant) running firmware older than NOE-R300.1.40.12.418 or SIP-R200.1.01.10.728.
  2. Verify if remote debugging or debug logging is enabled
    Access the deskphone administrative interface and check the debug configuration settings. Look for options labeled Remote Debug, Debug Logging, or Log Collection. Determine whether these features are currently active or enabled.
    Affected if Remote debugging or debug logging features are currently enabled on the device.
  3. Check authenticated access controls
    Review the user accounts and authentication settings in the deskphone admin interface. Identify which users have authenticated access and confirm whether weak or default credentials are in use. Verify that access is restricted to trusted personnel only.
    Affected if Multiple untrusted or unknown accounts have authenticated access, or default credentials remain in use.
  4. Confirm debug log directory permissions and symlink handling
    If administrative CLI or FTP/TFTP access is available, examine the debug log directory structure. Check whether the system permits symlink creation within debug directories by authenticated users.
    Affected if Authenticated users have write access to debug directories and can create symlinks.

A user is affected if their ALE deskphone runs a firmware version older than the fixed releases and has remote debugging or debug logging enabled with unrestricted authenticated access.

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

Apply vendor-supplied firmware updates (NOE-R300.1.40.12.418+ and SIP-R200.1.01.10.728+) that address the improper privilege management. Until patches are available, disable remote debugging features and restrict authenticated access to trusted personnel only.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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