ID CVE-2018-10847
Summary prosody before versions 0.10.2, 0.9.14 is vulnerable to an Authentication Bypass. Prosody did not verify that the virtual host associated with a user session remained the same across stream restarts. A user may authenticate to XMPP host A and migrate their authenticated session to XMPP host B of the same Prosody instance.
References
Vulnerable Configurations
  • Prosody 0.1.0
    cpe:2.3:a:prosody:prosody:0.1.0
  • Prosody 0.2.0
    cpe:2.3:a:prosody:prosody:0.2.0
  • Prosody 0.3.0
    cpe:2.3:a:prosody:prosody:0.3.0
  • Prosody 0.4.0
    cpe:2.3:a:prosody:prosody:0.4.0
  • Prosody 0.4.1
    cpe:2.3:a:prosody:prosody:0.4.1
  • Prosody 0.4.2
    cpe:2.3:a:prosody:prosody:0.4.2
  • Prosody 0.5.0
    cpe:2.3:a:prosody:prosody:0.5.0
  • Prosody 0.5.1
    cpe:2.3:a:prosody:prosody:0.5.1
  • Prosody 0.5.2
    cpe:2.3:a:prosody:prosody:0.5.2
  • Prosody 0.6.0
    cpe:2.3:a:prosody:prosody:0.6.0
  • Prosody 0.6.1
    cpe:2.3:a:prosody:prosody:0.6.1
  • Prosody 0.6.2
    cpe:2.3:a:prosody:prosody:0.6.2
  • Prosody 0.7.0
    cpe:2.3:a:prosody:prosody:0.7.0
  • Prosody 0.8.0
    cpe:2.3:a:prosody:prosody:0.8.0
  • Prosody 0.8.1
    cpe:2.3:a:prosody:prosody:0.8.1
  • Prosody 0.8.2
    cpe:2.3:a:prosody:prosody:0.8.2
  • Prosody 0.9.0
    cpe:2.3:a:prosody:prosody:0.9.0
  • Prosody 0.9.1
    cpe:2.3:a:prosody:prosody:0.9.1
  • Prosody 0.9.2
    cpe:2.3:a:prosody:prosody:0.9.2
  • Prosody 0.9.3
    cpe:2.3:a:prosody:prosody:0.9.3
  • Prosody 0.9.4
    cpe:2.3:a:prosody:prosody:0.9.4
  • Prosody 0.9.5
    cpe:2.3:a:prosody:prosody:0.9.5
  • Prosody 0.9.6
    cpe:2.3:a:prosody:prosody:0.9.6
  • Prosody 0.9.7
    cpe:2.3:a:prosody:prosody:0.9.7
  • Prosody 0.9.8
    cpe:2.3:a:prosody:prosody:0.9.8
  • Prosody 0.10.0
    cpe:2.3:a:prosody:prosody:0.10.0
  • Prosody 0.10.1
    cpe:2.3:a:prosody:prosody:0.10.1
CVSS
Base: 6.5
Impact:
Exploitability:
CWE CWE-287
CAPEC
  • Authentication Abuse
    An attacker obtains unauthorized access to an application, service or device either through knowledge of the inherent weaknesses of an authentication mechanism, or by exploiting a flaw in the authentication scheme's implementation. In such an attack an authentication mechanism is functioning but a carefully controlled sequence of events causes the mechanism to grant access to the attacker. This attack may exploit assumptions made by the target's authentication procedures, such as assumptions regarding trust relationships or assumptions regarding the generation of secret values. This attack differs from Authentication Bypass attacks in that Authentication Abuse allows the attacker to be certified as a valid user through illegitimate means, while Authentication Bypass allows the user to access protected material without ever being certified as an authenticated user. This attack does not rely on prior sessions established by successfully authenticating users, as relied upon for the "Exploitation of Session Variables, Resource IDs and other Trusted Credentials" attack patterns.
  • Exploiting Trust in Client (aka Make the Client Invisible)
    An attack of this type exploits a programs' vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by placing themselves in the communication channel between client and server such that communication directly to the server is possible where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.
  • Utilizing REST's Trust in the System Resource to Register Man in the Middle
    This attack utilizes a REST(REpresentational State Transfer)-style applications' trust in the system resources and environment to place man in the middle once SSL is terminated. Rest applications premise is that they leverage existing infrastructure to deliver web services functionality. An example of this is a Rest application that uses HTTP Get methods and receives a HTTP response with an XML document. These Rest style web services are deployed on existing infrastructure such as Apache and IIS web servers with no SOAP stack required. Unfortunately from a security standpoint, there frequently is no interoperable identity security mechanism deployed, so Rest developers often fall back to SSL to deliver security. In large data centers, SSL is typically terminated at the edge of the network - at the firewall, load balancer, or router. Once the SSL is terminated the HTTP request is in the clear (unless developers have hashed or encrypted the values, but this is rare). The attacker can utilize a sniffer such as Wireshark to snapshot the credentials, such as username and password that are passed in the clear once SSL is terminated. Once the attacker gathers these credentials, they can submit requests to the web service provider just as authorized user do. There is not typically an authentication on the client side, beyond what is passed in the request itself so once this is compromised, then this is generally sufficient to compromise the service's authentication scheme.
  • Man in the Middle Attack
    This type of attack targets the communication between two components (typically client and server). The attacker places himself in the communication channel between the two components. Whenever one component attempts to communicate with the other (data flow, authentication challenges, etc.), the data first goes to the attacker, who has the opportunity to observe or alter it, and it is then passed on to the other component as if it was never intercepted. This interposition is transparent leaving the two compromised components unaware of the potential corruption or leakage of their communications. The potential for Man-in-the-Middle attacks yields an implicit lack of trust in communication or identify between two components.
nessus via4
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2018-455803056D.NASL
    description Prosody 0.10.2 ============== See upstream's blog post at https://blog.prosody.im/prosody-0-10-2-security-release/ for a full overview of the release changes. Prosody 0.10.2 fixes a cross-host authentication vulnerability, CVE-2018-10847. The issue affects Prosody instances that have multiple virtual hosts (including anonymous authenticated hosts). All versions of Prosody before 0.9.14 and 0.10.2 are affected. A full security advisory is available at https://prosody.im/security/advisory_20180531 Security -------- - mod_c2s: Do not allow the stream ‘to’ to change across stream restarts (fixes #1147) Minor changes ------------- - mod_websocket: Store the request object on the session for use by other modules (fixes #1153) - mod_c2s: Avoid concatenating potential nil value (fixes #753) - core.certmanager: Allow all non-whitespace in service name (fixes #1019) - mod_disco: Skip code specific to disco on user accounts (avoids invoking usermanager, fixes #1150) - mod_bosh: Store the normalized hostname on session (fixes #1151) - MUC: Fix error logged when no persistent rooms present (fixes #1154) Dowstream ---------- - Changed log rotation from weekly/52 to local system defaults Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-10-18
    plugin id 110426
    published 2018-06-11
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=110426
    title Fedora 27 : prosody (2018-455803056d)
  • NASL family SuSE Local Security Checks
    NASL id OPENSUSE-2018-597.NASL
    description This update for prosody fixes the following issues : This security issue was fixed : - CVE-2018-10847: Prevent insufficient validation of client-provided parameters during XMPP stream restarts. Authenticated users may have overriden the realm associated with their session, potentially bypassing security policies and allowing impersonation (bsc#1094890).
    last seen 2019-02-21
    modified 2018-10-18
    plugin id 110472
    published 2018-06-12
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=110472
    title openSUSE Security Update : prosody (openSUSE-2018-597)
  • NASL family Debian Local Security Checks
    NASL id DEBIAN_DSA-4216.NASL
    description It was discovered that Prosody, a lightweight Jabber/XMPP server, does not properly validate client-provided parameters during XMPP stream restarts, allowing authenticated users to override the realm associated with their session, potentially bypassing security policies and allowing impersonation. Details can be found in the upstream advisory at https://prosody.im/security/advisory_20180531/
    last seen 2019-02-21
    modified 2018-11-13
    plugin id 110317
    published 2018-06-05
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=110317
    title Debian DSA-4216-1 : prosody - security update
  • NASL family SuSE Local Security Checks
    NASL id OPENSUSE-2018-596.NASL
    description This update for prosody to version 0.10.2 fixes the following issues : This security issue was fixed : - CVE-2018-10847: Prevent insufficient validation of client-provided parameters during XMPP stream restarts. Authenticated users may have overriden the realm associated with their session, potentially bypassing security policies and allowing impersonation (bsc#1094890). These non-security issues were fixed : - mod_websocket: Store the request object on the session for use by other modules - mod_c2s: Avoid concatenating potential nil value - core.certmanager: Allow all non-whitespace in service name - mod_disco: Skip code specific to disco on user accounts - mod_bosh: Store the normalized hostname on session - MUC: Fix error logged when no persistent rooms present
    last seen 2019-02-21
    modified 2018-10-18
    plugin id 110436
    published 2018-06-11
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=110436
    title openSUSE Security Update : prosody (openSUSE-2018-596)
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2018-18F8C6CE79.NASL
    description Prosody 0.10.2 ============== See upstream's blog post at https://blog.prosody.im/prosody-0-10-2-security-release/ for a full overview of the release changes. Prosody 0.10.2 fixes a cross-host authentication vulnerability, CVE-2018-10847. The issue affects Prosody instances that have multiple virtual hosts (including anonymous authenticated hosts). All versions of Prosody before 0.9.14 and 0.10.2 are affected. A full security advisory is available at https://prosody.im/security/advisory_20180531 Security -------- - mod_c2s: Do not allow the stream ‘to’ to change across stream restarts (fixes #1147) Minor changes ------------- - mod_websocket: Store the request object on the session for use by other modules (fixes #1153) - mod_c2s: Avoid concatenating potential nil value (fixes #753) - core.certmanager: Allow all non-whitespace in service name (fixes #1019) - mod_disco: Skip code specific to disco on user accounts (avoids invoking usermanager, fixes #1150) - mod_bosh: Store the normalized hostname on session (fixes #1151) - MUC: Fix error logged when no persistent rooms present (fixes #1154) Dowstream ---------- - Changed log rotation from weekly/52 to local system defaults Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2019-01-03
    plugin id 120258
    published 2019-01-03
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=120258
    title Fedora 28 : prosody (2018-18f8c6ce79)
refmap via4
confirm
debian DSA-4216
Last major update 30-07-2018 - 13:29
Published 30-07-2018 - 13:29
Last modified 17-10-2018 - 09:02
Back to Top