Apache httpd allows remote attackers to read secret data from process memory if the Limit directive can be set in a user’s .htaccess file, or if httpd.conf has certain misconfigurations, aka Optionsbleed. This affects the Apache HTTP Server through 2.2.34 and 2.4.x through 2.4.27. The attacker sends an unauthenticated OPTIONS HTTP request when attempting to read secret data. This is a use-after-free issue and thus secret data is not always sent, and the specific data depends on many factors including configuration. Exploitation with .htaccess can be blocked with a patch to the ap_limit_section function in server/core.c. **Recent assessments:** **h00die** at March 25, 2020 12:20am UTC reported: This vulnerability only happens when the `Limit` method is defined. This most likely isn’t very common in enterprise environments, and also the `Limit` method needs to be configured in an invalid way. Pending all that is true, which is unlikely, its possible to send an `OPTIONS` HTTP request and get back arbitrary memory. Unlike Heartbleed, we’re receiving back minimal memory and its also intermingled with the response. From my testing, against a test server, no useful data was found. It’s possible a production server on a very busy website may have divulged more useful data, but it would have to be minimal due to the returned buffer size. Assessed Attacker Value: 1 Assessed Attacker Value: 1Assessed Attacker Value: 5