dbcve.org
FonalityApplication

CVE-2016-2363

HIGH · 7.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 →
80/100
Remediation priority · High
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 uses weak permissions for the /var/www/rpc/surun script, which allows local users to obtain root access for unspecified command execution by leveraging access to the nobody account.

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

The Fonality trixbox Pro PBX software (versions 12.6 through 14.1i before June 2016) ships with weak file permissions on /var/www/rpc/surun, allowing the unprivileged 'nobody' user to execute this script. Since the script runs with root privileges, a local attacker with access to the nobody account can achieve unrestricted root command execution.

MitigationCorrect the file permissions on /var/www/rpc/surun to remove execute privileges from unprivileged users, or remove the script entirely if not required for business operations.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/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. Verify trixbox Pro version
    Check the installed version of Fonality trixbox Pro PBX (typically via 'rpm -q trixbox-pro' or checking /etc/trixbox/version)
    Affected if Version is 12.6, 12.8, or 14.1i
  2. Confirm vulnerable script exists
    Check if /var/www/rpc/surun file exists on the system
    Affected if The file /var/www/rpc/surun is present
  3. Inspect file permissions
    Run 'ls -la /var/www/rpc/surun' and examine the permission bits
    Affected if The file is executable by 'nobody' user or 'other' (world-executable)
  4. Verify script runs as root
    Check the file ownership and inspect the script header or run 'stat /var/www/rpc/surun' for uid/gid
    Affected if The script is owned by root and runs with root privileges

The environment is affected if trixbox Pro version is 12.6, 12.8, or 14.1i AND the /var/www/rpc/surun script exists with executable permissions accessible to the unprivileged 'nobody' user.

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

Correct the file permissions on /var/www/rpc/surun to remove execute privileges from unprivileged users, or remove the script entirely if not required for business operations.

Fix this in Fonality Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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