Skip to content
Fencer Intel
medium 5.3

CVE-2016-0756 json

The generate_dialback function in the mod_dialback module in Prosody before 0.9.10 does not properly separate fields when generating dialba…

published 2016-01-29 10 y ago modified 2026-06-17 4 mo ago also EUVD-2016-0776

cvss
5.3
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.1%
EPSS 2.1% chance of exploitation in 30 days, percentile 81%
public exploits
0
none known

Summary

The generate_dialback function in the mod_dialback module in Prosody before 0.9.10 does not properly separate fields when generating dialback keys, which allows remote attackers to spoof XMPP network domains via a crafted stream id and domain name that is included in the target domain as a suffix.

Patch / fix

  • prosody Debian 14, Debian 13, Debian 12 0.9.10-1

debian advisories DEBIAN-CVE-2016-0756

  • prosody Ubuntu 16.04 LTS 0.9.10-1

ubuntu advisories UBUNTU-CVE-2016-0756

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • prosody openSUSE Tumbleweed 0.9.11-1.1

opensuse advisories openSUSE-SU-2024:10489-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2016-0756 updated cvss 4.3

prosody: mod_dialback allows impersonation attacks

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.05% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 5.3 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.