Bug 1960340 (CVE-2021-32919) - CVE-2021-32919 prosody: undocumented dialback-without-dialback option insecure
Summary: CVE-2021-32919 prosody: undocumented dialback-without-dialback option insecure
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2021-32919
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1960341 1960355
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-13 17:12 UTC by Guilherme de Almeida Suckevicz
Modified: 2021-05-13 20:33 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-13 20:33:46 UTC
Embargoed:


Attachments (Terms of Use)

Description Guilherme de Almeida Suckevicz 2021-05-13 17:12:11 UTC
The undocumented option ‘dialback_without_dialback’ enabled an experimental feature for server-to-server authentication. A flaw in this feature meant it did not correctly authenticate remote servers, allowing a remote server to impersonate another server when this option is enabled.

The default configuration is not affected.
Configurations with the setting ‘dialback_without_dialback’ set to true are affected.

Reference:
https://prosody.im/security/advisory_20210512/

Comment 1 Guilherme de Almeida Suckevicz 2021-05-13 17:12:28 UTC
Created prosody tracking bugs for this issue:

Affects: fedora-all [bug 1960341]

Comment 2 Robert Scheck 2021-05-13 17:13:45 UTC
Well, this also affects epel-all

Comment 3 Guilherme de Almeida Suckevicz 2021-05-13 17:22:01 UTC
Created prosody tracking bugs for this issue:

Affects: epel-all [bug 1960355]

Comment 4 Product Security DevOps Team 2021-05-13 20:33:46 UTC
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.


Note You need to log in before you can comment on or make changes to this bug.