dbcve.org
PmaaApplication · Adtran

CVE-2018-19648

HIGH · 8.8 CVSS v3.0 Published 2019-03-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 ADTRAN PMAA 1.6.2-1, 1.6.3, and 1.6.4. NETCONF Access Management (NACM) allows unprivileged users to create privileged users and execute arbitrary commands via the use of the diagnostic-profile over RESTCONF.

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

ADTRAN PMAA versions 1.6.2-1, 1.6.3, and 1.6.4 contain a privilege escalation vulnerability in NETCONF Access Control Model (NACM). Unauthenticated or unprivileged users can leverage the diagnostic-profile functionality over RESTCONF to create privileged users and execute arbitrary operating system commands, effectively bypassing intended access controls.

MitigationUpgrade ADTRAN PMAA to a patched version that fixes the NACM bypass vulnerability, or apply vendor-supplied security updates. Restrict RESTCONF access to trusted networks until the patch is applied.

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
PmaaApplication
Affected:= 1.6.2= 1.6.3

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.0/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 installed PMAA version
    Access the ADTRAN PMAA administrative interface or check system information to retrieve the running software version. Common methods include reviewing the about page in the web UI, running 'show version' via CLI, or querying the system via SNMP.
    Affected if The installed version is 1.6.2, 1.6.3, or 1.6.4 exactly.
  2. Confirm RESTCONF is enabled
    Check the PMAA configuration for RESTCONF service status. This can be done via the CLI command 'show restconf' or by reviewing the NETCONF/RESTCONF configuration section in the web interface.
    Affected if RESTCONF is exposed and accessible (even on internal networks).
  3. Verify NACM configuration status
    Examine the NETCONF Access Control Model (NACM) settings by querying the running configuration for 'nacm' or 'netconf-access-control' settings. In the CLI, this may be visible via 'show running-config | include nacm'.
    Affected if NACM is present but the diagnostic-profile functionality allows bypass of user privilege restrictions.
  4. Review user accounts for unauthorized privileged users
    List all user accounts with administrative or privileged access by querying the user database via 'show users' in CLI or reviewing user management in the web UI. Look for accounts created that were not intentionally provisioned.
    Affected if Unexpected privileged user accounts exist that were not created by legitimate administrators.
  5. Inspect diagnostic-profile configurations
    Examine any diagnostic-profile configurations in the PMAA running configuration. Look for profiles that may have been created to leverage the vulnerability, often identifiable via 'show diagnostic-profile' or reviewing XML configuration exports.
    Affected if Diagnostic profiles exist that should not have been created, or profiles with unexpected system command execution permissions are present.

The environment is affected if the PMAA version is exactly 1.6.2, 1.6.3, or 1.6.4 AND RESTCONF is accessible, regardless of NACM configuration status.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade ADTRAN PMAA to a patched version that fixes the NACM bypass vulnerability, or apply vendor-supplied security updates. Restrict RESTCONF access to trusted networks until the patch is applied.

Fix this in Pmaa Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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