dbcve.org
FonalityApplication

CVE-2016-2362

CRITICAL · 9.8 CVSS v3.0 Published 2016-06-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Fonality (previously trixbox Pro) 12.6 through 14.1i before 2016-06-01 has a hardcoded password for the FTP account, which allows remote attackers to obtain access via a (1) FTP or (2) SSH connection.

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

Fonality (trixbox Pro) versions 12.6 through 14.1i contain a hardcoded password for a built-in FTP account. This credential is embedded in the firmware/software and cannot be changed through normal administration interfaces. Remote attackers can use this known password to authenticate via FTP or SSH and gain unauthorized access to the affected system.

MitigationImmediately disable or restrict the affected FTP/SSH service if not required for business operations. If the service is required, apply the vendor patch (released 2016-06-01) which removes the hardcoded credential and implement unique, rotated passwords for any service accounts.

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
FonalityApplication
Affected:= 12.6= 12.8= 14.1i

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.0/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. Identify the Fonality trixbox Pro version
    Access the system administration interface or run 'rpm -q trixbox-pro' or 'cat /etc/trixbox-version' from the command line to determine the installed version number
    Affected if The installed version is 12.6, 12.8, or falls within the range 12.6 through 14.1i
  2. Confirm FTP service is enabled
    Check if port 21 is listening: run 'netstat -tlnp | grep :21' or 'ss -tlnp | grep :21' on the system
    Affected if FTP service (port 21) is open and listening on a network interface accessible to attackers
  3. Confirm SSH service is enabled
    Check if port 22 is listening: run 'netstat -tlnp | grep :22' or 'ss -tlnp | grep :22' on the system
    Affected if SSH service (port 22) is open and listening on a network interface accessible to attackers
  4. Review system accounts for unmanaged built-in accounts
    List all system accounts with shell access using 'cat /etc/passwd' and compare against accounts created through normal administration. Look for accounts that cannot be changed via the web admin interface.
    Affected if A built-in FTP account exists that cannot be modified or disabled through the standard trixbox administration interface

The system is affected if it runs Fonality trixbox Pro versions 12.6 through 14.1i AND has FTP or SSH services exposed on accessible network interfaces.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately disable or restrict the affected FTP/SSH service if not required for business operations. If the service is required, apply the vendor patch (released 2016-06-01) which removes the hardcoded credential and implement unique, rotated passwords for any service accounts.

Recommended fix Moderate confidence

Any version released after 2016-06-01 (contact Fonality support for specific fixed version)

  1. 1. Identify the current Fonality installation version by logging into the administrative interface or checking the system documentation.
  2. 2. Contact Fonality support or consult their official release notes to confirm the specific version that includes the fix (released after June 1, 2016).
  3. 3. Before upgrading, perform a complete backup of the Fonality system including all configurations, user data, and phone system settings.
  4. 4. Review the Fonality upgrade documentation for your specific version to understand prerequisites and upgrade procedures.
  5. 5. Execute the upgrade following the vendor's recommended procedures, ensuring uninterrupted power supply during the process.
  6. 6. After upgrade completion, verify that the hardcoded FTP account credentials have been changed or are no longer present in the system.
  7. 7. Change all default administrative passwords and FTP/SSH credentials as a security best practice.
  8. 8. Test FTP and SSH access to confirm the system is functioning correctly with new credentials.
Caveat Review Fonality release notes for your specific version upgrade path as there may be telephony configuration changes or PBX feature modifications

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

Fix this in Fonality Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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