dbcve.org
Indoor Connect 8855 FirmwareOperating system · Ericsson

CVE-2025-40837

HIGH · 8.8 CVSS v3.1 Published 2025-09-25
Fix available
A fix is available. Upgrade to 2025.q2 or later.
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
Ericsson Indoor Connect 8855 contains a missing authorization vulnerability which if exploited can allow access to the system as a user with higher privileges than intended.

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

Ericsson Indoor Connect 8855 has a missing authorization vulnerability that allows authenticated users to access functionality or data beyond their intended privilege level, effectively enabling privilege escalation within the device's access control system.

MitigationApply vendor-provided firmware updates or patches that implement proper authorization checks and role-based access controls. If no patch is available, restrict network access to trusted users and monitor for unauthorized access attempts.

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
Indoor Connect 8855 FirmwareOperating system
Affected:< 2025.q2

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 the device model
    Access the device management interface or CLI and verify the exact product model name matches 'Ericsson Indoor Connect 8855'
    Affected if The device is not an Ericsson Indoor Connect 8855 model
  2. Locate the firmware version
    Check the device's system information, about page, or firmware/diagnostics section in the web interface, or run 'show version' or similar CLI command to retrieve the installed firmware version
    Affected if Unable to determine the firmware version from the device interface or CLI
  3. Compare version against affected range
    Compare the installed firmware version string to '< 2025.q2'. The version may be displayed as a date-based release (e.g., '2025.q1' or earlier) or a build number
    Affected if The installed firmware version is any version prior to 2025.q2, such as 2025.q1, 2024.x, or earlier releases
  4. Verify user role configuration
    Check the device's access control or user management settings to identify if multiple privilege levels or roles exist (e.g., admin, operator, viewer)
    Affected if The device supports role-based access and the vulnerability could allow lower-privilege users to escalate beyond their assigned role
  5. Review authentication logs
    Examine device audit or access logs for any anomalous activity where users accessed functions or data outside their expected privilege level
    Affected if Logs show authenticated users accessing functionality inconsistent with their assigned role

The environment is affected if the device is an Ericsson Indoor Connect 8855 running firmware version earlier than 2025.q2 and the device's role-based access control lacks proper authorization enforcement.

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
Upgrade available Upgrade to 2025.q2 or later
Fixed in 2025.q2
Interim mitigation

Apply vendor-provided firmware updates or patches that implement proper authorization checks and role-based access controls. If no patch is available, restrict network access to trusted users and monitor for unauthorized access attempts.

Recommended fix Moderate confidence

2025.q2

  1. 1. Identify the current firmware version of the Ericsson Indoor Connect 8855 device via the administrative web interface or CLI
  2. 2. Navigate to the official Ericsson support portal at www.ericsson.com and locate the Indoor Connect 8855 firmware download section
  3. 3. Download the firmware version 2025.q2 (or the latest stable release available)
  4. 4. Review the firmware release notes for any special upgrade instructions or prerequisites
  5. 5. Backup the current device configuration before proceeding with the upgrade
  6. 6. Access the device administration interface and navigate to the firmware upgrade section
  7. 7. Upload and apply the 2025.q2 firmware file
  8. 8. Verify the upgrade was successful by confirming the new firmware version in the device management interface

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

Fix this in Indoor Connect 8855 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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