p PatchFirst

CVE-2020-15260

CVE-2020-15260 · Existing TLS connections can be reused without checking remote hostname

Diese Seite enthält Fakten aus öffentlichen Sicherheitsquellen. Lesen Sie vor dem Aktualisieren die Originalmeldung.

PJSIP is a free and open source multimedia communication library written in C language implementing standard based protocols such as SIP, SDP, RTP, STUN, TURN, and ICE. In version 2.10 and earlier, PJSIP transport can be reused if they have the same IP address + port + protocol. However, this is insufficient for secure transport since it lacks remote hostname authentication. Suppose we have created a TLS connection to `sip.foo.com`, which has an IP address `100.1.1.1`. If we want to create a TLS connection to another hostname, say `sip.bar.com`, which has the same IP address, then it will reuse that existing connection, even though `100.1.1.1` does not have certificate to authenticate as `sip.bar.com`. The vulnerability allows for an insecure interaction without user awareness. It affects users who need access to connections to different destinations that translate to the same address, and allows man-in-the-middle attack if attacker can route a connection to another destination such as in the case of DNS spoofing.

CVSS 6.8 · Mittel · EPSS 1,0% · Korrektur verfügbar

Veröffentlicht
Aktualisiert

Technologie-Stack: system

Betroffene Produkte und Versionen

  • pjproject

    Softwareversionen
    • <= 2.10: Betroffen

    Keine Korrektur veröffentlicht

  • ring Debian:12

    Betroffene Versionsbereiche
    • ECOSYSTEM: < 20210112.2.b757bac~ds1-1

    Auf 20210112.2.b757bac~ds1-1 aktualisieren

  • pjproject Ubuntu:Pro:16.04:LTS

    Softwareversionen
    • 2.1.0.0.ast20130823-1
    • 2.1.0.0.ast20130823-1+deb8u1build0.16.04.1
    Betroffene Versionsbereiche
    • ECOSYSTEM: < 2.1.0.0.ast20130823-1+deb8u1ubuntu0.1~esm1

    Auf 2.1.0.0.ast20130823-1+deb8u1ubuntu0.1~esm1 aktualisieren

  • pjproject Ubuntu:Pro:18.04:LTS

    Softwareversionen
    • 2.6~dfsg-2
    • 2.7~dfsg-1
    • 2.7.1~dfsg-1
    • 2.7.1~dfsg-1build1
    • 2.7.2~dfsg-1
    Betroffene Versionsbereiche
    • ECOSYSTEM: < 2.7.2~dfsg-1ubuntu0.1~esm1

    Auf 2.7.2~dfsg-1ubuntu0.1~esm1 aktualisieren

Originalquellen

Prüfen Sie Ihren Server →