CVE-2023-39909
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 · uneditedEricsson Network Manager before 23.2 mishandles Access Control and thus unauthenticated low-privilege users can access the NCM application.
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 confidenceEricsson Network Manager before version 23.2 contains an access control vulnerability where unauthenticated low-privilege users can access the NCM (Network Configuration Management) application. This represents a direct authentication bypass allowing unauthorized access to sensitive network management functionality.
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< 23.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Ericsson Network Manager versionLocate the version information for your Ericsson Network Manager installation (typically found in the application GUI, about page, or system information file)Affected if The installed version is any version prior to 23.2 (e.g., 23.1, 22.x, earlier releases)
-
Verify NCM application authentication requirementsAttempt to access the Network Configuration Management (NCM) application endpoint without providing credentials or while authenticated as a low-privilege userAffected if The NCM application is accessible without proper authentication or allows low-privilege users to access administrative NCM functions
-
Check access control configuration for NCMReview the access control policies or role-based access settings within the Ericsson Network Manager administration interface to determine if NCM is properly protectedAffected if Access controls are misconfigured to allow unauthenticated or low-privilege access to NCM functionality
You are affected if your Ericsson Network Manager version is below 23.2 AND the NCM application is accessible without proper authentication or to low-privilege users.
Generated from the published advisory. Verify against your own configuration.
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 · scoped23.2
Upgrade Ericsson Network Manager to version 23.2 or later to resolve the access control misconfiguration. Verify the upgrade in a staging environment before production deployment.
23.2
- Verify current Ericsson Network Manager version is below 23.2
- Review Ericsson upgrade documentation and release notes for version 23.2
- Ensure proper backups of current configuration and database exist
- Schedule maintenance window for upgrade procedure
- Download Ericsson Network Manager version 23.2 from authorized Ericsson distribution channels
- Execute upgrade to version 23.2 following official Ericsson upgrade procedures
- Verify upgrade completed successfully by checking version number
- Test that access control functions properly after upgrade - verify low-privilege users can no longer access NCM without proper authentication
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-39909 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-39909 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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