CVE-2016-0736 Details

CVE-2016-0736

Published: 2017-07-27
Last Modified: 2021-06-06
CVE Author: NIST National Vulnerability Database
CVE Assigner: security@apache.org
Summary

In Apache HTTP Server versions 2.4.0 to 2.4.23, mod_session_crypto was encrypting its data/cookie using the configured ciphers with possibly either CBC or ECB modes of operation (AES256-CBC by default), hence no selectable or builtin authenticated encryption. This made it vulnerable to padding oracle attacks, particularly with CBC.

Analysis
Common Vulnerability Score System v2.0
Severity Medium
Base Score 5/10
Exploit Score 10/10
Access Vector Network
Access Complexity Low
Authentication None
Impact Score 2.9/10
Confidentiality Impact Partial
Availability Impact None
Integrity Impact None
Vector String AV:N/AC:L/Au:N/C:P/I:N/A:N
Common Vulnerability Score System v3.1
Severity High
Base Score 7.5/10
Exploit Score 3.9/10
Access Vector Network
Access Complexity Low
Privileges Required None
Impact Score 3.6/10
Confidentiality Impact High
Availability Impact None
Integrity Impact None
Scope Unchanged
User Interaction None
Vector String CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Products Reported
CPE Vulnerable Start Excluding
cpe:2.3:a:apache:http_server:2.4.0:*:*:*:*:*:*:* Yes - -
cpe:2.3:a:apache:http_server:2.4.1:*:*:*:*:*:*:* Yes - -
cpe:2.3:a:apache:http_server:2.4.10:*:*:*:*:*:*:* Yes - -
cpe:2.3:a:apache:http_server:2.4.12:*:*:*:*:*:*:* Yes - -
cpe:2.3:a:apache:http_server:2.4.6:*:*:*:*:*:*:* Yes - -
cpe:2.3:a:apache:http_server:2.4.7:*:*:*:*:*:*:* Yes - -
cpe:2.3:a:apache:http_server:2.4.20:*:*:*:*:*:*:* Yes - -
cpe:2.3:a:apache:http_server:2.4.21:*:*:*:*:*:*:* Yes - -
cpe:2.3:a:apache:http_server:2.4.8:*:*:*:*:*:*:* Yes - -
cpe:2.3:a:apache:http_server:2.4.9:*:*:*:*:*:*:* Yes - -
cpe:2.3:a:apache:http_server:2.4.22:*:*:*:*:*:*:* Yes - -
cpe:2.3:a:apache:http_server:2.4.23:*:*:*:*:*:*:* Yes - -
cpe:2.3:a:apache:http_server:2.4.2:*:*:*:*:*:*:* Yes - -
cpe:2.3:a:apache:http_server:2.4.3:*:*:*:*:*:*:* Yes - -
cpe:2.3:a:apache:http_server:2.4.14:*:*:*:*:*:*:* Yes - -
cpe:2.3:a:apache:http_server:2.4.16:*:*:*:*:*:*:* Yes - -
cpe:2.3:a:apache:http_server:2.4.19:*:*:*:*:*:*:* Yes - -
References

https://httpd.apache.org/security/vulnerabilities_24.html#CVE-2016-0736
https://security.gentoo.org/glsa/201701-36
https://h20566.www2.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-hpesbux
http://www.securitytracker.com/id/1037508
http://www.securityfocus.com/bid/95078
https://www.exploit-db.com/exploits/40961/
https://www.tenable.com/security/tns-2017-04
http://www.debian.org/security/2017/dsa-3796
https://support.apple.com/HT208221
https://access.redhat.com/errata/RHSA-2017:1414
https://access.redhat.com/errata/RHSA-2017:1413
https://access.redhat.com/errata/RHSA-2017:1161
https://access.redhat.com/errata/RHSA-2017:0906
http://rhn.redhat.com/errata/RHSA-2017-1415.html
https://security.netapp.com/advisory/ntap-20180423-0001/
https://lists.apache.org/thread.html/56c2e7cc9deb1c12a843d0dc251ea7fd3e7e80293cde02fcd65
https://lists.apache.org/thread.html/84a3714f0878781f6ed84473d1a503d2cc382277e1004502092
https://lists.apache.org/thread.html/rd18c3c43602e66f9cdcf09f1de233804975b9572b0456cc582
https://lists.apache.org/thread.html/re3d27b6250aa8548b8845d314bb8a350b3df326cacbbfdfe4d
https://lists.apache.org/thread.html/rc998b18880df98bafaade071346690c2bc1444adaa1a1ea464
https://lists.apache.org/thread.html/rf6449464fd8b7437704c55f88361b66f12d5b5f90bcce66af4
https://lists.apache.org/thread.html/r04e89e873d54116a0635ef2f7061c15acc5ed27ef7500997be
https://lists.apache.org/thread.html/re1e3a24664d35bcd0a0e793e0b5fc6ca6c107f99a1b2c545c5
https://lists.apache.org/thread.html/r9f93cf6dde308d42a9c807784e8102600d0397f5f834890708
https://lists.apache.org/thread.html/rb14daf9cc4e28d18cdc15d6a6ca74e565672fabf7ad8954107
https://lists.apache.org/thread.html/rcc44594d4d6579b90deccd4536b5d31f099ef563df39b094be
https://lists.apache.org/thread.html/r76142b8c5119df2178be7c2dba88fde552eedeec37ea993dfc

CVE ID
CVE-2016-0736
Published
2017-07-27
Modified
2021-06-06
CVSSv2.0
Medium
CVSSv3.1
High
PCI Compliance
Fail
US-CERT Alert
No
CWE
CWE-310

Free Vulnerability Scanning, Assessment and Management

Mageni's Platform is packed with all the features you need to scan, assess and manage vulnerabilities like this - it is free, open source, lightning fast, reliable and scalable.

Router
Servers
Laptop
Database
Group
Cloud

Frequently Asked Questions

No, you can scan concurrently as many assets as you want. Please note that you must be aware of the hardware requeriments of the platform to ensure a good performance.

No, you can add as many assest as you want. It doesn't matters if you have millions of assets, we won't charge you for that.

No. The software is completely free. We have no intention to charge you to use the software, in fact - it completely goes against our beliefs and business model.

A vulnerability is defined in the ISO 27002 standard as “A weakness of an asset or group of assets that can be exploited by one or more threats” (International Organization for Standardization, 2005)

We generate revenue by providing support and other services for customers that require a subscription so they get guaranteed support and enterprise services. To use Mageni's Platform is completely free, with no limits at all.

Yes. Mageni understands that there are professionals and businesses that need commercial support so Mageni provides an active support subscription with everything needed to run Mageni's Platform reliably and securely. More than software, it's access to security experts, knowledge resources, security updates, and support tools you can't get anywhere else. The subscription includes:

  • Ongoing delivery
    • Patches
    • Bug fixes
    • Updates
    • Upgrades
  • Technical support
    • 24/7 availability
    • Unlimited Incidents
    • Specialty-based routing
    • Multi-Channel
  • Commitments
    • Software certifications
    • Software assurance
    • SLA

No, we don't store the information of your vulnerabilities in our servers.

Vulnerability management is the process in which vulnerabilities in IT are identified and the risks of these vulnerabilities are evaluated. This evaluation leads to correcting the vulnerabilities and removing the risk or a formal risk acceptance by the management of an organization. The term vulnerability management is often confused with vulnerability scanning. Despite the fact both are related, there is an important difference between the two. Vulnerability scanning consists of using a computer program to identify vulnerabilities in networks, computer infrastructure or applications. Vulnerability management is the process surrounding vulnerability scanning, also taking into account other aspects such as risk acceptance, remediation etc. Source: "Implementing a Vulnerability Management Process". SANS Institute.

I am ready to start scanning for vulnerabilities