Overview
- Microsoft Activex Control Download
- Microsoft Activex Control In Windows 10
- Host An ActiveX Control In WPF | Microsoft Docs
- If you are not able to load Active X control then you need to change the security for your browser, or put the url into trusted sites. On other browsers like Firefox, it redirects away from the v7 site and doesn't prompt for Active X at all.
- ActiveX controls are Internet Explorer’s version of plug-ins. For example, Internet Explorer’s Flash player is an ActiveX control. Unfortunately, ActiveX controls have been a significant source of security problems. ActiveX controls are essentially pieces of software and have access to your entire computer if you opt to install and run them.
Nov 19, 2018 ActiveX controls are designed for use both in ordinary ActiveX control containers and on the Internet, in World Wide Web pages. You can create ActiveX controls either with MFC, described here, or with the Active Template Library (ATL). An ActiveX control can draw itself in its own window, respond to events (such as mouse clicks), and be managed through an interface that includes properties and methods similar to those in Automation objects. To edit the ActiveX control, make sure that you are in design mode. On the Developer tab, in the Controls group, click Design Mode. To set the control properties, on the Developer tab, in the Controls group, click Properties. You can also right-click the control, and then click Properties. The Properties dialog box appears.
| Finding ID | Version | Rule ID | IA Controls | Severity |
|---|---|---|---|---|
| V-70869 | DTOO191 | SV-85493r1_rule | Medium |
| Description |
|---|
| This policy setting specifies the Microsoft ActiveX« initialization security level for all Microsoft Office applications. ActiveX controls can adversely affect a computer directly. In addition, malicious code can be used to compromise an ActiveX control and attack a computer. To indicate the safety of an ActiveX control, developers can denote them as Safe For Initialization (SFI). SFI indicates that a control is safe to open and run, and that it is not capable of causing a problem for any computer, regardless of whether it has persisted data values or not. If a control is not marked SFI, it is possible that the control could adversely affect a computer--or it could mean that the developers did not test the control in all situations and are not sure whether it might be compromised in the future. If you enable this policy setting, you can set the ActiveX security level to a number between 1 and 6. These security levels are as follows: 1 - Regardless of how the control is marked, load it and use the persisted values (if any). This setting does not prompt the user. 2 - If SFI, load the control in safe mode and use persisted values (if any). If not SFI, load in unsafe mode with persisted values (if any), or use the default (first-time initialization) settings. This level is similar to the default configuration, but does not prompt the user. 3 - If SFI, load the control in unsafe mode and use persisted values (if any). If not SFI, prompt the user and advise them that it is marked unsafe. If the user chooses No at the prompt, do not load the control. Otherwise, load it with default (first-time initialization) settings. 4 - If SFI, load the control in safe mode and use persisted values (if any). If not SFI, prompt the user and advise them that it is marked unsafe. If the user chooses No at the prompt, do not load the control. Otherwise, load it with default (first-time initialization) settings. 5 - If SFI, load the control in unsafe mode and use persisted values (if any). If not SFI, prompt the user and advise them that it is marked unsafe. If the user chooses No at the prompt, do not load the control. Otherwise, load it with persisted values. 6 - If SFI, load the control in safe mode and use persisted values (if any). If not SFI, prompt the user and advise them that it is marked unsafe. If the user chooses No at the prompt, do not load the control. Otherwise, load it with persisted values. If you disable or do not configure this policy setting, if a control is marked SFI, the application loads the control in safe mode and uses persisted values (if any). If the control is not marked SFI, the application loads the control in unsafe mode with persisted values (if any), or uses the default (first-time initialization) settings. In both situations, the Message Bar informs users that the controls have been disabled and prompts them to respond. Important - Some ActiveX controls do not respect the safe mode registry setting, and therefore might load persisted data even though you configure this setting to instruct the control to use safe mode. This setting only increases security for ActiveX controls that are accurately marked as SFI. In situations that involve malicious or poorly designed code, an ActiveX control might be inaccurately marked as SFI. |
| STIG | Date |
|---|---|
| Microsoft Office System 2016 Security Technical Implementation Guide | 2016-11-02 |
Details
| Check Text ( C-71313r2_chk ) |
|---|
| Verify the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2016 -> Security Settings 'ActiveX Control Initialization' is set to 'Disabled'. Procedure: Use the Windows Registry Editor to navigate to the following key: HKCUSoftwarePoliciesMicrosoftOfficeCommonSecurity Criteria: If the value UFIControls exists, this is a finding. |
Microsoft Activex Control Download
| Fix Text (F-77201r1_fix) |
|---|
| Set the policy value for User Configuration -> Administrative Templates -> Microsoft Office 2016 -> Security Settings 'ActiveX Control Initialization' to 'Disabled'. |
While the Windows Forms Designer in Visual Studio is optimized to host Windows Forms controls, you can also put ActiveX controls on Windows Forms.
Caution
There are performance limitations for Windows Forms when ActiveX controls are added to them.
Microsoft Activex Control In Windows 10
Before you add ActiveX controls to your form, you must add them to the Toolbox. For more information, see COM Components, Customize Toolbox Dialog Box.
Add an ActiveX control to your Windows Form
To add an ActiveX control to your Windows Form, double-click the control on the Toolbox.
Visual Studio adds all references to the control in your project. For more information about things to keep in mind when using ActiveX controls on Windows Forms, see Considerations When Hosting an ActiveX Control on a Windows Form.
Host An ActiveX Control In WPF | Microsoft Docs
Note
The Windows Forms ActiveX Control Importer (AxImp.exe) creates event arguments of a different type than expected upon importation of ActiveX dynamic link libraries. The arguments created by AxImp.exe are similar to the following: Invoke(object sender, DWebBrowserEvents2_ProgressChangeEvent e), when Invoke(object sender, DWebBrowserEvents2_ProgressChangeEventArgs e) is expected. Be aware that this irregularity does not prevent code from functioning normally. For details, see Windows Forms ActiveX Control Importer (Aximp.exe).