dbcve.org
Accel PppApplication

CVE-2022-0982

CRITICAL · 9.8 CVSS v3.1 Published 2022-03-16
Fix available
A fix is available. Upgrade to after 1.12.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
The telnet_input_char function in opt/src/accel-pppd/cli/telnet.c suffers from a memory corruption vulnerability, whereby user input cmdline_len is copied into a fixed buffer b->buf without any bound checks. If the server connects with a malicious client, crafted client requests can remotely trigger this vulnerability.

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

A buffer overflow vulnerability exists in the telnet_input_char function in accel-pppd's telnet CLI component. The cmdline_len user input is copied into a fixed-size buffer (b->buf) without any bounds checking, allowing a malicious telnet client to trigger memory corruption by sending specially crafted requests with excessive input length.

MitigationImplement proper bounds checking before copying cmdline_len into b->buf, ensuring the input length does not exceed the buffer size. Consider using safe string functions like strncpy or implementing explicit length validation with appropriate error handling.

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
Accel PppApplication
Affected:<= 1.12.0

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Check if accel-pppd is installed
    Run 'accel-pppd --version' or check package manager (e.g., 'dpkg -l | grep accel-pppd' or 'rpm -qa | grep accel-pppd')
    Affected if accel-pppd is installed and version is 1.12.0 or lower
  2. Verify the installed version number
    Compare the installed version to the affected range: versions <= 1.12.0
    Affected if Installed version is 1.12.0 or any version below 1.12.0
  3. Determine if telnet CLI is enabled
    Inspect accel-pppd configuration files (typically in /etc/accel-ppp.conf) for '[telnet]' or 'telnet=' sections, and check if the telnet server is bound to an interface
    Affected if The telnet CLI component is enabled and accessible in the configuration
  4. Check if telnet port is listening
    Run 'netstat -tlnp | grep accel' or 'ss -tlnp | grep accel' to see if accel-pppd is listening on port 23 (default telnet)
    Affected if accel-pppd is listening on a telnet port and accepts remote connections
  5. Identify the telnet configuration settings
    Review the accel-ppp configuration for 'telnet' module settings, specifically looking for bind parameters and whether authentication is required
    Affected if Telnet interface is exposed without proper access controls or is bound to accessible network interfaces

User is affected if accel-pppd version 1.12.0 or lower is installed AND the telnet CLI component is enabled and accessible.

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 1.12.0
Interim mitigation

Implement proper bounds checking before copying cmdline_len into b->buf, ensuring the input length does not exceed the buffer size. Consider using safe string functions like strncpy or implementing explicit length validation with appropriate error handling.

Recommended fix Moderate confidence

Accel PPP version 1.12.1 or latest stable release

  1. 1. Identify the current Accel PPP version installed using package manager or ./version check
  2. 2. Upgrade to the latest stable release (version 1.12.1 or later) which contains the security fix for the telnet.c out-of-bounds write vulnerability
  3. 3. After upgrade, verify the telnet component is running the patched binary by checking /opt/src/accel-pppd/cli/telnet.c in the source
  4. 4. Restart the accel-pppd service to load the patched version
  5. 5. Test telnet functionality to ensure the service operates normally after the update
Caveat Minor - point release upgrade; should retain configuration compatibility but test in staging first

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

Fix this in Accel Ppp Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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