p PatchFirst

PatchFirst · Latest vulnerabilities

openafs vulnerabilities

Vulnerabilities published for openafs in the last 30 days: 0. Listed in the KEV catalogue: 0.

Filter vulnerabilities
Clear filters

Vulnerabilities: 9

  1. CVE-2024-10396

    Medium · CVSS 6.5EPSS 0.56%No fix published

    Fileserver crash and possible information leak on StoreACL/FetchACL

    An authenticated user can provide a malformed ACL to the fileserver's StoreACL RPC, causing the fileserver to crash, possibly expose uninitialized memory, and possibly store garbage data in the audit log. Malformed ACLs provided in responses to client FetchACL RPCs can cause client processes to crash and possibly expose uninitialized memory into other ACLs stored on the server.

    Published Updated
  2. CVE-2018-16949

    High · CVSS 7.5EPSS 3.08%No fix published

    CVE-2018-16949

    An issue was discovered in OpenAFS before 1.6.23 and 1.8.x before 1.8.2. Several data types used as RPC input variables were implemented as unbounded array types, limited only by the inherent 32-bit length field to 4 GB. An unauthenticated attacker could send, or claim to send, large input values and consume server resources waiting for those inputs, denying service to other valid connections.

    Published Updated
  3. CVE-2018-16948

    High · CVSS 7.5EPSS 1.99%No fix published

    CVE-2018-16948

    An issue was discovered in OpenAFS before 1.6.23 and 1.8.x before 1.8.2. Several RPC server routines did not fully initialize their output variables before returning, leaking memory contents from both the stack and the heap. Because the OpenAFS cache manager functions as an Rx server for the AFSCB service, clients are also susceptible to information leakage. For example, RXAFSCB_TellMeAboutYourself leaks kernel memory and KAM_ListEntry leaks kaserver memory.

    Published Updated
  4. CVE-2018-16947

    Critical · CVSS 9.8EPSS 2.6%No fix published

    CVE-2018-16947

    An issue was discovered in OpenAFS before 1.6.23 and 1.8.x before 1.8.2. The backup tape controller (butc) process accepts incoming RPCs but does not require (or allow for) authentication of those RPCs. Handling those RPCs results in operations being performed with administrator credentials, including dumping/restoring volume contents and manipulating the backup database. For example, an unauthenticated attacker can replace any volume's content with arbitrary data.

    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →