CVE-2007-6424
Summary
| CVE | CVE-2007-6424 |
|---|---|
| State | PUBLISHED |
| Assigner | mitre |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2007-12-18 19:46:00 UTC |
| Updated | 2026-04-23 00:35:47 UTC |
| Description | registry.pl in Fonality Trixbox 2.0 PBX products, when running in certain environments, reads and executes a set of commands from a remote web site without sufficiently validating the origin of the commands, which allows remote attackers to disable trixbox and execute arbitrary commands via a DNS spoofing attack. |
Risk And Classification
CVSS v2.0 Breakdown
Access Vector
NetworkAccess Complexity
MediumAuthentication
NoneConfidentiality
NoneIntegrity
PartialAvailability
NoneAV:N/AC:M/Au:N/C:N/I:P/A:N
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Netfortris | Trixbox | 2.0 | All | All | All |
Vendor Declared Affected Products
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| osvdb.org/44136 | af854a3a-2127-422b-91ae-364da2661108 | osvdb.org | |
| Voice of VOIPSA » Blog Archive » Trixbox contains “phone home” code to retrieve arbitrary commands to execute? | af854a3a-2127-422b-91ae-364da2661108 | voipsa.org | |
| [VOIPSEC] Trixbox Arbitrary Command Execution Vulnerability | af854a3a-2127-422b-91ae-364da2661108 | voipsa.org | |
| [VOIPSEC] trixbox vulnerability fluff | af854a3a-2127-422b-91ae-364da2661108 | voipsa.org | |
| Trixbox Phones Home | trixbox | af854a3a-2127-422b-91ae-364da2661108 | www.trixbox.org | |
| [VOIPSEC] trixbox vuln (CVE-2007-6424) - PoC exploit code | af854a3a-2127-422b-91ae-364da2661108 | voipsa.org | |
| The SuperUnknown » Trixbox phones home | af854a3a-2127-422b-91ae-364da2661108 | www.superunknown.org | Exploit, URL Repurposed |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.