McAfee Security Bulletin – Application Control / Change Control for Linux update fixes a write protection and execution bypass vulnerability (CVE-2013-7460 and CVE-2013-7461)
最終更新: 5/11/2017
概要
| Who Should Read This Document: | Technical and Security Personnel |
| Impact of Vulnerability: | Write Protections Bypass Execution Bypass |
| CVE Number: | CVE-2013-7460 CVE-2013-7461 |
| US CERT Number: | None |
| Severity Rating: | Medium |
| Overall CVSS Score: | 4.3 |
| Recommendations: | Install the provided hotfix. |
| Security Bulletin Replacement: | None |
| Caveats: | None |
| Affected Software: |
|
| Location of Updated Software: | http://www.mcafee.com/us/downloads |
説明
A write protection and execution bypass vulnerability in McAfee (now Intel Security) Application Control (MAC) 6.1.0 for Linux and earlier allows authenticated users to change binaries that are part of the Application Control whitelist and allows execution of binaries via specific conditions.
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-7460
CVE-2013-7461
A write protection and execution bypass vulnerability in McAfee (now Intel Security) Change Control (MCC) 6.1.0 for Linux and earlier allows authenticated users to change files that are part of write protection rules via specific conditions.
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-7461
A vulnerability exists in McAfee Application Control (MAC) and McAfee Change Control (MCC) that allows a user to bypass protection on a Linux platform. The attacker must be an authenticated user to exploit this flaw.
For MAC, the vulnerability allows change to binaries that are part of the Application Control whitelist and allows execution of binaries under specific conditions.
For MCC, the vulnerability allows change to files that are part of write protection rules under specific conditions.
This vulnerability exists in the following product versions:
- MAC 6.1.0 (Linux platform only)
- MCC 6.1.0 (Linux platform only)
McAfee considers this to be medium severity vulnerability and should be patched soon. A hotfix has been created to address this vulnerability.
修正
| Product | Type | File Name / Information | Release Date |
| MAC 6.1.0 | Hotfix | SOLIDCOR610-9500_LNX.zip | September 18, 2013 |
| MCC 6.1.0 | Hotfix | SOLIDCOR610-9500_LNX.zip | September 18, 2013 |
MAC & MCC 6.1.0 download Instructions
- Launch Internet Explorer.
- Navigate to: http://www.mcafee.com/us/downloads.
- Provide your valid McAfee grant number.
- Click your product suite.
- Click the applicable product (see table above) and click I Agree.
- Click the Hotfix or Patches tab or click the link to download the product .ZIP file under Download on the Software Downloads screen.
For instructions on how to download McAfee products, documentation, security updates, patches, or hotfixes, see article KB56057.
For instructions on how to install / upgrade this patch, review the Release Notes and the Installation Guide (available from the Documentation tab) following the same steps above.
回避策
サポート
1-800-338-8754
http://www.mcafee.com/us/about/contact-us.aspx#ht=tab-techsupport
よくある質問(FAQ)
McAfee Application Control 6.1.0 for Linux.
Affected Versions:
- 6.1.0 Build 9474 (RTW)
- 6.1.0 Build 9492 (Hotfix 1)
- 6.1.0 Build 9494 (Hotfix 2)
- 6.1.0 Build 9500 (Hotfix 3) or later
What issues does this hotfix address?
- 900515: Solidcore whitelisted binary may be modified by non-trusted source and can be executed under specific condition
- 906552: Solidcore write-protected file may be modified by non-trusted source under specific condition
Does this vulnerability affect McAfee enterprise products?
Yes, MAC & MCC for Linux are Enterprise products.
How do I know if my McAfee Application Control / McAfee Change Control for Linux are vulnerable or not?
Use the following instructions to determine the version of MAC / MCC you are currently using for Linux:
- For ePO managed deployments, use ePO queries to get the number of systems with different versions of Solidcore on Linux platform.
- For standalone deployments, use: sadmin version.
What is CVSS?
CVSS, or Common Vulnerability Scoring System, is the result of the National Infrastructure Advisory Council’s effort to standardize a system of assessing the criticality of a vulnerability. This system offers an unbiased criticality score that customers can use to judge how critical a vulnerability is and plan accordingly. For more information, please visit the CVSS website at: http://www.first.org/cvss/.
What are the CVSS scoring metrics that have been used?
| Base Score | 5.2 |
| Related exploit range (AccessVector) | Local |
| Attack complexity (AccessComplexity) | Low |
| Level of authentication needed (Authentication) | Single Instance |
| Confidentiality impact | None |
| Integrity impact | Partial |
| Availability impact | Complete |
| Temporal Score | 4.3 |
| Availability of exploit (Exploitability) | High |
| Type of fix available (RemediationLevel) | Official fix |
| Level of verification that vulnerability exists (ReportConfidence) | Confirmed |
NOTE: CVSS version 2.0 vector was used to generate this score.
http://nvd.nist.gov/cvss.cfm?calculator&version=2&vector=(AV:L/AC:L/Au:S/C:N/I:P/A:C/E:F/RL:O/RC:C)
What has McAfee done to resolve the issue?
McAfee has released a hotfix to address this security flaw.
Where do I download the fix?
The fix can be downloaded from: http://www.mcafee.com/us/downloads
Users will need to provide their McAfee Grant Number to initiate the download.
How does McAfee respond to this and any other security flaws?
McAfee’s key priority is the security of our customers. In the event that a vulnerability is found within any of McAfee’s software, we work closely with the relevant security research group to ensure rapid and effective development of a fix and communication plan. McAfee is an active member of the Organization for Internet Safety (OIS), which is dedicated to developing guidelines and best practices for the reporting and fixing of software vulnerabilities.
McAfee only publishes product vulnerability bulletins together with an actionable workaround, patch, or hotfix; otherwise we would simply be informing the hacker community that our products are a target, putting our customers at greater risk.
リソース
To submit Beta feedback on any McAfee product, email: mcafee_beta@mcafee.com
For contact information, go to: http://www.mcafee.com/uk/about/contact-us.aspx
For copyright, trademark attributions, and license information, go to: http://us.mcafee.com/root/aboutUs.asp?id=copyright
For patents protecting this product, see your product documentation.
免責事項
The information provided in this security bulletin is provided as is without warranty of any kind. McAfee disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall McAfee or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if McAfee or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
Any future product release dates mentioned in this bulletin are intended to outline our general product direction and they should not be relied on in making a purchasing decision. The product release dates are for information purposes only, and may not be incorporated into any contract. The product release dates are not a commitment, promise or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at our sole discretion and may be changed or cancelled at any time.
