Security Bulletin – Application Control / Change Control for Linux update fixes a write protection and execution bypass vulnerability (CVE-2013-7460 and CVE-2013-7461)
Last Modified: 5/4/2022
Summary
| 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: | Product Downloads site |
Description
A write protection and execution bypass vulnerability in Application Control 6.1.0 for Linux and earlier allows authenticated users to change binaries that are part of the Application Control allow list 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 Change Control 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 Application Control and Change Control that allows a user to bypass protection on a Linux platform. The attacker must be an authenticated user to exploit this flaw.
For Application Control, the vulnerability allows change to binaries that are part of the Application Control whitelist and allows execution of binaries under specific conditions.
For Change Control, the vulnerability allows change to files that are part of write protection rules under specific conditions.
This vulnerability exists in the following product versions:
- Application Control 6.1.0 (Linux platform only)
- Change Control 6.1.0 (Linux platform only)
We consider this to be medium severity vulnerability. A hotfix has been created to address this vulnerability.
Remediation
| Product | Type | File Name / Information | Release Date |
| Application Control 6.1.0 | Hotfix | SOLIDCOR610-9500_LNX.zip | September 18, 2013 |
| MCC 6.1.0 | Hotfix | SOLIDCOR610-9500_LNX.zip | September 18, 2013 |
Application Control and Change Control 6.1.0 download Instructions
- Launch Internet Explorer.
- Go to the Product Downloads site.
- Provide your valid 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 to download product updates and hotfixes, see KB56057 - How to download Enterprise product updates and documentation. Review the Release Notes and Installation Guide for instructions on how to install these updates. All documentation is available at our Product Documentation site.
Workaround
Frequently Asked Questions (FAQs)
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
How do I know if my Application Control or Change Control for Linux versions are vulnerable or not?
Use the following instructions to determine the version of Application Control and Change Control 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, visit the CVSS website.
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 have you done to resolve the issue?
We've released a hotfix to address this security flaw.
Where do I download the fix?
Download the fix from the Product Downloads site. You will need to provide a valid gran number to initiate the download.
Where can I find a list of all Security Bulletins?
All Security Bulletins are published on our Knowledge Center. Security Bulletins are retired (removed) once a product is both End of Sale and End of Support (End of Life).
How do I report a product vulnerability to you?
If you have information about a security issue or vulnerability with a product, follow the instructions provided in KB95563 - Report a vulnerability.
How do you respond to this and any other reported security flaws?
Our key priority is the security of our customers. If a vulnerability is found within any of our software or services, we work closely with the relevant security software development team to ensure the rapid and effective development of a fix and communication plan.
We only publish Security Bulletins if they include something actionable such as a workaround, mitigation, version update, or hotfix. Otherwise, we would simply be informing the hacker community that our products are a target, putting our customers at greater risk. For products that are updated automatically, a non-actionable Security Bulletin might be published to acknowledge the discoverer.
To view our PSIRT policy, see KB95564 - About PSIRT.
Resources
- If you are a registered user, type your User ID and Password, and then click Log In.
- If you are not a registered user, click Register and complete the fields to have your password and instructions emailed to you.
Disclaimer
The information provided in this Security Bulletin is provided as is without warranty of any kind. We disclaim all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall we or our suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits, or special damages, even if we or our suppliers have been advised of the possibility of such damages. Some states don't allow the exclusion or limitation of liability for consequential or incidental damages, so the preceding limitation may not apply.
Any future product release dates mentioned in this Security Bulletin are intended to outline our general product direction, and they shouldn't 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 aren't 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 remain at our sole discretion and may be changed or canceled at any time.
