dbcve.org
Operations Support System Radio And Core FirmwareOperating system · Ericsson

CVE-2021-32569

MEDIUM · 6.1 CVSS v3.1 Published 2021-10-14
Fix available
A fix is available. Upgrade to after 18b or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
In OSS-RC systems of the release 18B and older customer documentation browsing libraries under ALEX are subject to Cross-Site Scripting. This problem is completely resolved in new Ericsson library browsing tool ELEX used in systems like Ericsson Network Manager. NOTE: This vulnerability only affects products that are no longer supported by the maintainer. Ericsson Network Manager is a new generation OSS system which OSS-RC customers shall upgrade to

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

Cross-Site Scripting (XSS) vulnerability in the ALEX documentation browsing libraries of Ericsson OSS-RC systems (release 18B and older). The vulnerability allows injection of malicious scripts through the documentation browsing feature.

MitigationMigrate from the deprecated OSS-RC system to the newer Ericsson Network Manager platform which uses the ELEX library browsing tool. This is the only supported remediation path as the affected OSS-RC 18B and older versions are end-of-life.

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
Operations Support System Radio And Core FirmwareOperating system
Affected:<= 18b

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Confirm Ericsson OSS-RC is deployed
    Identify if your environment contains Ericsson OSS-RC (Operations Support System Radio And Core) systems. Check system inventory, documentation, or contact Ericsson for system identification assistance.
    Affected if The system is running Ericsson OSS-RC
  2. Check OSS-RC version
    Determine the installed OSS-RC version by accessing the system management interface, checking system logs, or using Ericsson-supplied version inspection commands. Compare against version 18B.
    Affected if The installed version is 18B or any version older than 18B
  3. Verify ALEX documentation browsing is accessible
    Check if the ALEX documentation browsing library feature is enabled or accessible in the OSS-RC system. This may require reviewing system configuration, user access settings, or documentation browsing module status.
    Affected if The ALEX documentation browsing feature is enabled or accessible to users

Your environment is affected if you run Ericsson OSS-RC version 18B or older and the ALEX documentation browsing feature is enabled or accessible, as this creates the conditions for XSS exploitation via malicious script injection.

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 a release after 18b
Interim mitigation

Migrate from the deprecated OSS-RC system to the newer Ericsson Network Manager platform which uses the ELEX library browsing tool. This is the only supported remediation path as the affected OSS-RC 18B and older versions are end-of-life.

Recommended fix High confidence

Ericsson Network Manager (ENM) - the next-generation OSS system with fixed ELEX library browsing tool

  1. 1. Assess current OSS-RC system version and confirm it is 18B or older
  2. 2. Contact Ericsson sales or support to obtain Ericsson Network Manager (ENM) licensing and installation media
  3. 3. Plan migration strategy from OSS-RC to Ericsson Network Manager, as this is a major system upgrade
  4. 4. Perform a full backup of current OSS-RC configuration and customer documentation
  5. 5. Execute migration to Ericsson Network Manager following Ericsson documentation
  6. 6. Verify that the ALEX documentation browsing library has been replaced with the fixed ELEX tool
  7. 7. Validate that the XSS vulnerability is no longer present in the new system
  8. 8. Update documentation and operational procedures to reflect the new system
Caveat This is a major system migration from OSS-RC to Ericsson Network Manager; significant architectural changes, potential workflow modifications, and comprehensive testing are required before production deployment

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

Fix this in Operations Support System Radio And Core Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA6.0 h
50.0 hours of engineering $8,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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