UBUNTU-CVE-2016-7143: High severity ubuntu/charybdis vulnerability

Q: Who is exposed to this issue?

Charybdis deployments using a version before 3.5.3 are exposed if they use the affected SASL authentication code in modules/m_sasl.c. The issue can be reached remotely over the network.

Q: What does an attacker need to exploit it?

The attacker does not need prior privileges or user interaction, but exploitation requires crafting an AUTHENTICATE parameter and has high attack complexity. Successful exploitation can spoof certificate fingerprints and allow login as another user.

Q: What is the potential impact of successful exploitation?

A successful attacker may authenticate as a different user. The reported severity vector indicates high impact to confidentiality, integrity, and availability.

Q: How can I determine whether my deployment is affected?

Check whether the installed Charybdis version is earlier than 3.5.3 and whether the deployment includes the m_sasl.c SASL authentication module. Systems meeting both conditions should be treated as affected.

Published Sep 21, 2016

Updated

The mauthenticate function in modules/msasl.c in Charybdis before 3.5.3 allows remote attackers to spoof certificate fingerprints and consequently log in as another user via a crafted AUTHENTICATE parameter.

Affected Software

2 affected componentsFixes available

ubuntu/charybdis<3.4.2-3ubuntu0.1~esm1

3.4.2-3ubuntu0.1~esm1

ubuntu/charybdis<3.5.0-1ubuntu0.1~esm1

3.5.0-1ubuntu0.1~esm1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade ubuntu/charybdis to a version that resolves this vulnerability.
Fixed in 3.4.2-3ubuntu0.1~esm1
Upgrade
Upgrade ubuntu/charybdis to a version that resolves this vulnerability.
Fixed in 3.5.0-1ubuntu0.1~esm1

Event History

Sep 21, 2016

CVE Published

via OSV·02:25 PM

Data Sourced

via OSV·02:25 PM

DescriptionSeverityAffected Software

Frequently Asked Questions

Who is exposed to this issue?

Charybdis deployments using a version before 3.5.3 are exposed if they use the affected SASL authentication code in modules/m_sasl.c. The issue can be reached remotely over the network.

What does an attacker need to exploit it?

The attacker does not need prior privileges or user interaction, but exploitation requires crafting an AUTHENTICATE parameter and has high attack complexity. Successful exploitation can spoof certificate fingerprints and allow login as another user.

What is the potential impact of successful exploitation?

A successful attacker may authenticate as a different user. The reported severity vector indicates high impact to confidentiality, integrity, and availability.

How can I determine whether my deployment is affected?

Check whether the installed Charybdis version is earlier than 3.5.3 and whether the deployment includes the m_sasl.c SASL authentication module. Systems meeting both conditions should be treated as affected.

UBUNTU-CVE-2016-7143: High severity ubuntu/charybdis vulnerability

Affected Software

Remediation

Event History

Frequently Asked Questions

Who is exposed to this issue?

What does an attacker need to exploit it?

What is the potential impact of successful exploitation?

How can I determine whether my deployment is affected?

Company

Resources

Contact

Frequently Asked Questions

Who is exposed to this issue?

What does an attacker need to exploit it?

What is the potential impact of successful exploitation?

How can I determine whether my deployment is affected?