ID CVE-2015-7763
Summary rx/rx.c in OpenAFS 1.5.75 through 1.5.78, 1.6.x before 1.6.15, and 1.7.x before 1.7.33 does not properly initialize padding at the end of an Rx acknowledgement (ACK) packet, which allows remote attackers to obtain sensitive information by (1) conducting a replay attack or (2) sniffing the network.
References
Vulnerable Configurations
  • OpenAFS 1.5.75
    cpe:2.3:a:openafs:openafs:1.5.75
  • OpenAFS 1.5.76
    cpe:2.3:a:openafs:openafs:1.5.76
  • OpenAFS 1.5.77
    cpe:2.3:a:openafs:openafs:1.5.77
  • OpenAFS 1.5.78
    cpe:2.3:a:openafs:openafs:1.5.78
  • OpenAFS 1.6.0
    cpe:2.3:a:openafs:openafs:1.6.0
  • OpenAFS 1.6.1
    cpe:2.3:a:openafs:openafs:1.6.1
  • OpenAFS 1.6.2
    cpe:2.3:a:openafs:openafs:1.6.2
  • OpenAFS 1.6.3
    cpe:2.3:a:openafs:openafs:1.6.3
  • OpenAFS 1.6.4
    cpe:2.3:a:openafs:openafs:1.6.4
  • OpenAFS 1.6.5
    cpe:2.3:a:openafs:openafs:1.6.5
  • OpenAFS 1.6.6
    cpe:2.3:a:openafs:openafs:1.6.6
  • OpenAFS 1.6.5.1
    cpe:2.3:a:openafs:openafs:1.6.5.1
  • OpenAFS 1.6.5.2
    cpe:2.3:a:openafs:openafs:1.6.5.2
  • OpenAFS 1.6.2.1
    cpe:2.3:a:openafs:openafs:1.6.2.1
  • OpenAFS 1.6.7
    cpe:2.3:a:openafs:openafs:1.6.7
  • OpenAFS 1.6.8
    cpe:2.3:a:openafs:openafs:1.6.8
  • OpenAFS 1.6.9
    cpe:2.3:a:openafs:openafs:1.6.9
  • OpenAFS 1.6.10
    cpe:2.3:a:openafs:openafs:1.6.10
  • OpenAFS 1.6.11
    cpe:2.3:a:openafs:openafs:1.6.11
  • OpenAFS 1.6.12
    cpe:2.3:a:openafs:openafs:1.6.12
  • OpenAFS 1.6.13
    cpe:2.3:a:openafs:openafs:1.6.13
  • OpenAFS 1.6.14
    cpe:2.3:a:openafs:openafs:1.6.14
  • OpenAFS 1.7.1
    cpe:2.3:a:openafs:openafs:1.7.1
  • OpenAFS 1.7.10
    cpe:2.3:a:openafs:openafs:1.7.10
  • OpenAFS 1.7.11
    cpe:2.3:a:openafs:openafs:1.7.11
  • OpenAFS 1.7.12
    cpe:2.3:a:openafs:openafs:1.7.12
  • OpenAFS 1.7.13
    cpe:2.3:a:openafs:openafs:1.7.13
  • OpenAFS 1.7.14
    cpe:2.3:a:openafs:openafs:1.7.14
  • OpenAFS 1.7.15
    cpe:2.3:a:openafs:openafs:1.7.15
  • OpenAFS 1.7.16
    cpe:2.3:a:openafs:openafs:1.7.16
  • OpenAFS 1.7.17
    cpe:2.3:a:openafs:openafs:1.7.17
  • OpenAFS 1.7.18
    cpe:2.3:a:openafs:openafs:1.7.18
  • OpenAFS 1.7.19
    cpe:2.3:a:openafs:openafs:1.7.19
  • OpenAFS 1.7.2
    cpe:2.3:a:openafs:openafs:1.7.2
  • OpenAFS 1.7.20
    cpe:2.3:a:openafs:openafs:1.7.20
  • OpenAFS 1.7.21
    cpe:2.3:a:openafs:openafs:1.7.21
  • OpenAFS 1.7.22
    cpe:2.3:a:openafs:openafs:1.7.22
  • OpenAFS 1.7.23
    cpe:2.3:a:openafs:openafs:1.7.23
  • OpenAFS 1.7.24
    cpe:2.3:a:openafs:openafs:1.7.24
  • OpenAFS 1.7.25
    cpe:2.3:a:openafs:openafs:1.7.25
  • OpenAFS 1.7.26
    cpe:2.3:a:openafs:openafs:1.7.26
  • OpenAFS 1.7.27
    cpe:2.3:a:openafs:openafs:1.7.27
  • OpenAFS 1.7.28
    cpe:2.3:a:openafs:openafs:1.7.28
  • OpenAFS 1.7.29
    cpe:2.3:a:openafs:openafs:1.7.29
  • OpenAFS 1.7.3
    cpe:2.3:a:openafs:openafs:1.7.3
  • OpenAFS 1.7.30
    cpe:2.3:a:openafs:openafs:1.7.30
  • OpenAFS 1.7.31
    cpe:2.3:a:openafs:openafs:1.7.31
  • OpenAFS 1.7.4
    cpe:2.3:a:openafs:openafs:1.7.4
  • OpenAFS 1.7.8
    cpe:2.3:a:openafs:openafs:1.7.8
CVSS
Base: 5.0 (as of 09-11-2015 - 10:35)
Impact:
Exploitability:
CWE CWE-200
CAPEC
  • Subverting Environment Variable Values
    The attacker directly or indirectly modifies environment variables used by or controlling the target software. The attacker's goal is to cause the target software to deviate from its expected operation in a manner that benefits the attacker.
  • Footprinting
    An attacker engages in probing and exploration activity to identify constituents and properties of the target. Footprinting is a general term to describe a variety of information gathering techniques, often used by attackers in preparation for some attack. It consists of using tools to learn as much as possible about the composition, configuration, and security mechanisms of the targeted application, system or network. Information that might be collected during a footprinting effort could include open ports, applications and their versions, network topology, and similar information. While footprinting is not intended to be damaging (although certain activities, such as network scans, can sometimes cause disruptions to vulnerable applications inadvertently) it may often pave the way for more damaging attacks.
  • 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.
  • Browser Fingerprinting
    An attacker carefully crafts small snippets of Java Script to efficiently detect the type of browser the potential victim is using. Many web-based attacks need prior knowledge of the web browser including the version of browser to ensure successful exploitation of a vulnerability. Having this knowledge allows an attacker to target the victim with attacks that specifically exploit known or zero day weaknesses in the type and version of the browser used by the victim. Automating this process via Java Script as a part of the same delivery system used to exploit the browser is considered more efficient as the attacker can supply a browser fingerprinting method and integrate it with exploit code, all contained in Java Script and in response to the same web page request by the browser.
  • Session Credential Falsification through Prediction
    This attack targets predictable session ID in order to gain privileges. The attacker can predict the session ID used during a transaction to perform spoofing and session hijacking.
  • Reusing Session IDs (aka Session Replay)
    This attack targets the reuse of valid session ID to spoof the target system in order to gain privileges. The attacker tries to reuse a stolen session ID used previously during a transaction to perform spoofing and session hijacking. Another name for this type of attack is Session Replay.
  • Using Slashes in Alternate Encoding
    This attack targets the encoding of the Slash characters. An attacker would try to exploit common filtering problems related to the use of the slashes characters to gain access to resources on the target host. Directory-driven systems, such as file systems and databases, typically use the slash character to indicate traversal between directories or other container components. For murky historical reasons, PCs (and, as a result, Microsoft OSs) choose to use a backslash, whereas the UNIX world typically makes use of the forward slash. The schizophrenic result is that many MS-based systems are required to understand both forms of the slash. This gives the attacker many opportunities to discover and abuse a number of common filtering problems. The goal of this pattern is to discover server software that only applies filters to one version, but not the other.
Access
VectorComplexityAuthentication
NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
PARTIAL NONE NONE
nessus via4
  • NASL family Debian Local Security Checks
    NASL id DEBIAN_DLA-342.NASL
    description Several vulnerabilities have been found and solved in the distributed file system OpenAFS : CVE-2015-3282 vos leaked stack data clear on the wire when updating vldb entries. CVE-2015-3283 OpenAFS allowed remote attackers to spoof bos commands via unspecified vectors. CVE-2015-3285 pioctl wrongly used the pointer related to the RPC, allowing local users to cause a denial of service (memory corruption and kernel panic) via a crafted OSD FS command. CVE-2015-6587 vlserver allowed remote authenticated users to cause a denial of service (out-of-bounds read and crash) via a crafted regular expression in a VL_ListAttributesN2 RPC. CVE-2015-7762 and CVE-2015-7763 ('Tattletale') John Stumpo found that Rx ACK packets leaked plaintext of packets previously processed. For Debian 6 'Squeeze', these problems have been fixed in openafs version 1.4.12.1+dfsg-4+squeeze4. We recommend that you upgrade your OpenAFS packages. Learn more about the Debian Long Term Support (LTS) Project and how to apply these updates at: https://wiki.debian.org/LTS/ NOTE: Tenable Network Security has extracted the preceding description block directly from the DLA security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-07-06
    plugin id 86920
    published 2015-11-19
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=86920
    title Debian DLA-342-1 : openafs security update
  • NASL family Scientific Linux Local Security Checks
    NASL id SL_20151021_OPENAFS_ON_SL5_X.NASL
    description This release fixes the high impact security vulnerability named 'Tattletale' The packet paylod of Rx ACK packets is not fully initialized, leaking plaintext from packets previously processed.
    last seen 2019-02-21
    modified 2018-12-28
    plugin id 86671
    published 2015-10-30
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=86671
    title Scientific Linux Security Update : openafs on SL5.x, SL6.x, SL7.x i386/x86_64
  • NASL family Debian Local Security Checks
    NASL id DEBIAN_DSA-3387.NASL
    description John Stumpo discovered that OpenAFS, a distributed file system, does not fully initialize certain network packets before transmitting them. This can lead to a disclosure of the plaintext of previously processed packets.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 86681
    published 2015-11-02
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=86681
    title Debian DSA-3387-1 : openafs - security update
  • NASL family FreeBSD Local Security Checks
    NASL id FREEBSD_PKG_017A493F7DB611E5A76214DAE9D210B8.NASL
    description The OpenAFS development team reports : When constructing an Rx acknowledgment (ACK) packet, Andrew-derived Rx implementations do not initialize three octets of data that are padding in the C language structure and were inadvertently included in the wire protocol (CVE-2015-7762). Additionally, OpenAFS Rx in versions 1.5.75 through 1.5.78, 1.6.0 through 1.6.14, and 1.7.0 through 1.7.32 include a variable-length padding at the end of the ACK packet, in an attempt to detect the path MTU, but only four octets of the additional padding are initialized (CVE-2015-7763).
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 86645
    published 2015-10-29
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=86645
    title FreeBSD : openafs -- information disclosure (017a493f-7db6-11e5-a762-14dae9d210b8)
refmap via4
confirm
debian DSA-3387
mlist [OpenAFS-announce] 20151028 OpenAFS security release 1.6.15 available
sectrack 1034039
Last major update 07-12-2016 - 13:25
Published 06-11-2015 - 16:59
Back to Top