Vulnerabilities > CVE-2014-2927 - Improper Authentication vulnerability in F5 products
Attack vector
UNKNOWN Attack complexity
UNKNOWN Privileges required
UNKNOWN Confidentiality impact
UNKNOWN Integrity impact
UNKNOWN Availability impact
UNKNOWN Summary
The rsync daemon in F5 BIG-IP 11.6 before 11.6.0, 11.5.1 before HF3, 11.5.0 before HF4, 11.4.1 before HF4, 11.4.0 before HF7, 11.3.0 before HF9, and 11.2.1 before HF11 and Enterprise Manager 3.x before 3.1.1 HF2, when configured in failover mode, does not require authentication, which allows remote attackers to read or write to arbitrary files via a cmi request to the ConfigSync IP address.
Vulnerable Configurations
Common Weakness Enumeration (CWE)
Common Attack Pattern Enumeration and Classification (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.
Exploit-Db
description | F5 Big-IP - Unauthenticated rsync Access. Remote exploit for hardware platform |
file | exploits/hardware/remote/34465.txt |
id | EDB-ID:34465 |
last seen | 2016-02-03 |
modified | 2014-08-29 |
platform | hardware |
port | 22 |
published | 2014-08-29 |
reporter | Security-Assessment.com |
source | https://www.exploit-db.com/download/34465/ |
title | F5 Big-IP - Unauthenticated rsync Access |
type | remote |
Nessus
NASL family Misc. NASL id F5_RSYNC_RCE.NASL description The rsync daemon on the remote F5 Networks host is affected by an authentication bypass vulnerability when configured in failover mode. An unauthenticated, remote attacker can exploit this, via a cmi request to the ConfigSync IP address, to read or write arbitrary files. Nessus was able to confirm that a module on the remote rsync daemon allows writing files to the root of the file system. An attacker can overwrite last seen 2020-06-01 modified 2020-06-02 plugin id 78427 published 2014-10-14 reporter This script is Copyright (C) 2014-2018 Tenable Network Security, Inc. source https://www.tenable.com/plugins/nessus/78427 title F5 Networks rsync RCE code # # (C) Tenable Network Security, Inc. # include("compat.inc"); if (description) { script_id(78427); script_version("1.5"); script_cvs_date("Date: 2018/07/11 17:09:26"); script_cve_id("CVE-2014-2927"); script_bugtraq_id(69461); script_xref(name:"EDB-ID", value:"34465"); script_name(english:"F5 Networks rsync RCE"); script_summary(english:"Checks for writeable rsync modules."); script_set_attribute(attribute:"synopsis", value: "The remote host is running a rsync daemon that allows a user to upload arbitrary files."); script_set_attribute(attribute:"description", value: "The rsync daemon on the remote F5 Networks host is affected by an authentication bypass vulnerability when configured in failover mode. An unauthenticated, remote attacker can exploit this, via a cmi request to the ConfigSync IP address, to read or write arbitrary files. Nessus was able to confirm that a module on the remote rsync daemon allows writing files to the root of the file system. An attacker can overwrite '/root/.ssh/authorized_keys' and obtain ssh access, allowing the execution of arbitrary code with the privileges of the root user."); # http://support.f5.com/kb/en-us/solutions/public/15000/200/sol15236.html script_set_attribute(attribute:"see_also", value:"http://www.nessus.org/u?c5d7c6b5"); # http://www.security-assessment.com/files/documents/advisory/F5_Unauthenticated_rsync_access_to_Remote_Root_Code_Execution.pdf script_set_attribute(attribute:"see_also", value:"http://www.nessus.org/u?7c390e25"); script_set_attribute(attribute:"solution", value: "Disable the rsync daemon."); script_set_cvss_base_vector("CVSS2#AV:N/AC:M/Au:N/C:C/I:C/A:C"); script_set_cvss_temporal_vector("CVSS2#E:POC/RL:OF/RC:C"); script_set_attribute(attribute:"exploitability_ease", value:"Exploits are available"); script_set_attribute(attribute:"exploit_available", value:"true"); script_set_attribute(attribute:"vuln_publication_date", value:"2014/08/28"); script_set_attribute(attribute:"patch_publication_date", value:"2014/08/28"); script_set_attribute(attribute:"plugin_publication_date", value:"2014/10/14"); script_set_attribute(attribute:"plugin_type", value:"remote"); script_set_attribute(attribute:"cpe", value:"cpe:/h:f5:big-ip"); script_set_attribute(attribute:"exploited_by_nessus", value:"true"); script_end_attributes(); script_category(ACT_GATHER_INFO); script_family(english:"Misc."); script_copyright(english:"This script is Copyright (C) 2014-2018 Tenable Network Security, Inc."); script_dependencies("rsync_writeable.nasl"); script_require_ports("Services/rsyncd", 873); exit(0); } include("audit.inc"); include("global_settings.inc"); include("misc_func.inc"); include("byte_func.inc"); include("string.inc"); include("rsync.inc"); port = get_service(svc:"rsyncd", default:873, exit_on_fail:TRUE); modules = get_kb_list_or_exit("rsyncd/" + port + "/writeable/*"); cmi = FALSE; csync = FALSE; if (!isnull(modules)) { foreach module (modules) { name = base64_decode(str:module); if (name == "cmi") cmi = TRUE; else if (name == "csync") csync = TRUE; } } if (!cmi && !csync) audit(AUDIT_LISTEN_NOT_VULN, "Rsync daemon", port); # connect and get a file to ensure this is F5 csync_version_file = NULL; cmi_version_file = NULL; if (cmi) { soc = rsync_init(port:port); if (soc) { version_file = rsync_get_file(socket:soc, module:"cmi", file_name:"VERSION"); if ("Product: BIG-IP" >< version_file || "Product: EM" >< version_file || "Product: BIG-IQ" >< version_file) { cmi_version_file = version_file; } close(soc); } } if (csync) { soc = rsync_init(port:port, exit_if_fail:TRUE); if (soc) { version_file = rsync_get_file(socket:soc, module:"csync", file_name:"VERSION"); if ( "Product: BIG-IP" >< version_file || "Product: EM" >< version_file || "Product: BIG-IQ" >< version_file ) csync_version_file = version_file; close(soc); } } if (!isnull(cmi_version_file) || !isnull(csync_version_file)) { if (report_verbosity > 0) { report = ""; if (!isnull(cmi_version_file)) { report += '\n' + "Nessus was able to download VERSION from the writeable 'cmi' Rsync module: " + '\n' + '\n' + cmi_version_file; } if (!isnull(csync_version_file)) { report += '\n' + "Nessus was able to download VERSION from the writeable 'csync' Rsync module :" + '\n' + '\n' + csync_version_file; } security_hole(port:port, extra:report); } else security_hole(port); exit(0); } else audit(AUDIT_HOST_NOT, "F5 Networks");
NASL family F5 Networks Local Security Checks NASL id F5_BIGIP_SOL15236.NASL description The rsync daemon in F5 BIG-IP 11.6 before 11.6.0, 11.5.1 before HF3, 11.5.0 before HF4, 11.4.1 before HF4, 11.4.0 before HF7, 11.3.0 before HF9, and 11.2.1 before HF11 and Enterprise Manager 3.x before 3.1.1 HF2, when configured in failover mode, does not require authentication, which allows remote attackers to read or write to arbitrary files via a cmi request to the ConfigSync IP address. (CVE-2014-2927) Impact A remote unauthenticated user with access to the ConfigSync IP address may be allowed full read/write access to the file system. Exploitation of this vulnerability could lead to unauthenticated root access. last seen 2020-06-01 modified 2020-06-02 plugin id 78167 published 2014-10-10 reporter This script is Copyright (C) 2014-2019 and is owned by Tenable, Inc. or an Affiliate thereof. source https://www.tenable.com/plugins/nessus/78167 title F5 Networks BIG-IP : ConfigSync IP Rsync full file system access vulnerability (K15236)
Saint
bid | 69461 |
description | F5 rsync daemon ConfigSync interface cmi module vulnerability |
osvdb | 110595 |
title | f5_configsync_rsync |
type | remote |