dbcve.org
Evolved Packet GatewayApplication · Ericsson

CVE-2022-47531

HIGH · 8.8 CVSS v3.1 Published 2023-12-05
Fix available
A fix is available. Upgrade to 2.16 / 3.25 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
An issue was discovered in Ericsson Evolved Packet Gateway (EPG) versions 3.x before 3.25 and 2.x before 2.16, allows authenticated users to bypass system CLI and execute commands they are authorized to execute directly in the UNIX shell.

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 users on Ericsson EPG devices can bypass the intended CLI interface and execute commands they're authorized for directly in the underlying UNIX shell. This bypasses the controlled CLI environment, potentially allowing command manipulation or privilege escalation beyond the intended CLI restrictions.

MitigationUpgrade Ericsson EPG to version 3.25 (for 3.x branches) or 2.16 (for 2.x branches) as specified in the vendor advisory to patch the CLI bypass vulnerability.

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
Evolved Packet GatewayApplication
Affected:>= 2.0, < 2.16>= 3.0, < 3.25

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
    Check the system model or product name displayed in the device CLI or management interface to confirm it is an Ericsson Evolved Packet Gateway
    Affected if Device is not an Ericsson EPG (not affected)
  2. Determine the installed software version
    Use the device's CLI command to display the software version (typically via 'show version' or similar command in the EPG CLI)
    Affected if Version is >= 2.0 and < 2.16, OR >= 3.0 and < 3.25
  3. Verify if shell escape is accessible
    Attempt to access the underlying UNIX shell from within the EPG CLI using standard escape sequences or shell invocation methods, or review audit logs for such attempts
    Affected if Shell access is possible from within the authenticated CLI session (vulnerability is present)
  4. Review CLI session logs for unauthorized command execution
    Examine CLI session logs or audit trails for commands executed outside the normal CLI command structure, particularly those that appear to invoke system shell commands
    Affected if Logs show commands executed directly in the shell environment rather than through the intended CLI parser

The environment is affected if the device is an Ericsson EPG running version 2.0-2.15 or 3.0-3.24, and shell access can be obtained from within an authenticated CLI session.

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 2.16 / 3.25 or later
Fixed in 2.163.25
Interim mitigation

Upgrade Ericsson EPG to version 3.25 (for 3.x branches) or 2.16 (for 2.x branches) as specified in the vendor advisory to patch the CLI bypass vulnerability.

Recommended fix High confidence

EPG 2.16 or EPG 3.25 (or later releases in respective branches)

  1. Schedule a maintenance window for the EPG upgrade
  2. Back up the current EPG configuration according to Ericsson documentation
  3. Obtain the fixed version upgrade package (EPG 2.16 for 2.x branch or EPG 3.25 for 3.x branch) from authorized Ericsson support channels
  4. Upload the upgrade package to the EPG system following Erricsson's standard upgrade procedure
  5. Execute the upgrade using Erricson's documented upgrade process
  6. Verify successful upgrade by checking the EPG version displays 2.16 or 3.25 (or later)
  7. Confirm the CLI bypass vulnerability is remediated by testing that authorized commands execute through the proper CLI interface

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

Fix this in Evolved Packet Gateway Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
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,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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