Cyber · Trackr The Free Compliance Library
⌘K
DoD Compliance · STIG

Microsoft Publisher 2010 Security Technical Implementation Guide

V1R12 · · · Released 24 Jul 2024 · 17 rules
Compare

Pick two releases to diff their requirements.

View

Open a previous version of this STIG.

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via e-mail to the following address: disa.stig_spt@mail.mil.
Digest of Updates vs. V1R9 · 24 Jul 2015 +17 −17

Comparison against the immediately-prior release (V1R9). Rule matching uses the Group Vuln ID. Content-change detection compares the rule’s description, check, and fix text after stripping inline markup — cosmetic-only edits aren’t flagged.

Added rules 17

  • V-242261 Medium Disabling of user name and password syntax from being used in URLs must be enforced.
  • V-242262 Medium Enabling IE Bind to Object functionality must be present.
  • V-242263 Medium Saved from URL mark to assure Internet zone processing must be enforced.
  • V-242264 Medium Navigation to URL's embedded in Office products must be blocked.
  • V-242265 Medium Scripted Window Security must be enforced.
  • V-242266 Medium Add-on Management functionality must be allowed.
  • V-242267 Medium Application add-ins must be signed by Trusted Publisher.
  • V-242268 Medium Data Execution Prevention must be enforced.
  • V-242269 Medium Links that invoke instances of IE from within an Office product must be blocked.
  • V-242270 Medium Trust Bar Notifications for unsigned application add-ins must be blocked.
  • V-242271 Medium File Downloads must be configured for proper restrictions.
  • V-242272 Medium Protection from zone elevation must be enforced.
  • V-242273 Medium ActiveX Installs must be configured for proper restriction.
  • V-242274 Medium Warning Bar settings for VBA macros must be configured.
  • V-242275 Medium Fatally corrupt files must be blocked from opening.
  • V-242276 Medium The Publisher Automation Security Level must be configured for high security.
  • V-265898 High The version of Microsoft Publisher running on the system must be a supported version.

Removed rules 17

  • V-17173 Medium Disabling of user name and password syntax from being used in URLs must be enforced.
  • V-17174 Medium Enabling IE Bind to Object functionality must be present.
  • V-17175 Medium Saved from URL mark to assure Internet zone processing must be enforced.
  • V-17183 Medium Navigation to URL's embedded in Office products must be blocked.
  • V-17184 Medium Links that invoke instances of IE from within an Office product must be blocked.
  • V-17187 Medium Trust Bar Notifications for unsigned application add-ins must be blocked.
  • V-17545 Medium Warning Bar settings for VBA macros must be configured.
  • V-26584 Medium Add-on Management functionality must be allowed.
  • V-26585 Medium Protection from zone elevation must be enforced.
  • V-26586 Medium ActiveX Installs must be configured for proper restriction.
  • V-26587 Medium File Downloads must be configured for proper restrictions.
  • V-26588 Medium Scripted Window Security must be enforced.
  • V-26589 Medium Application add-ins must be signed by Trusted Publisher.
  • V-26590 Medium Data Execution Prevention must be enforced.
  • V-26625 Medium Disable UI extending from documents and templates must be disallowed.
  • V-26707 Medium Fatally corrupt files must be blocked from opening.
  • V-26708 Medium The Publisher Automation Security Level must be configured for high security.
Sort by
b
Disabling of user name and password syntax from being used in URLs must be enforced.
SC-18 - Medium - CCI-001170 - V-242261 - SV-242261r961092_rule
RMF Control
SC-18
Severity
M
CCI
CCI-001170
Version
DTOO104 - Publisher
Vuln IDs
  • V-242261
  • V-17173
Rule IDs
  • SV-242261r961092_rule
  • SV-33895
The Uniform Resource Locator (URL) standard allows user authentication to be included in URL strings in the form http://username:password@example.com. A malicious user might use this URL syntax to create a hyperlink that appears to open a legitimate Web site but actually opens a deceptive (spoofed) Web site. For example, the URL http://www.wingtiptoys.com@example.com appears to open http://www.wingtiptoys.com but actually opens http://example.com. To protect users from such attacks, Internet Explorer usually blocks any URLs using this syntax. This functionality can be controlled separately for instances of Internet Explorer spawned by Office applications (for example, if a user clicks a link in an Office document or selects a menu option that loads a Web page). If user names and passwords in URLs are allowed, users could be diverted to dangerous Web pages, which could pose a security risk.
Checks: C-45536r710617_chk

The policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2010 (Machine) -> Security Settings -> IE Security "Disable user name and password" must be "Enabled" and a check in the "mspub.exe" check box must be present. Procedure: Use the Windows Registry Editor to navigate to the following key: HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_HTTP_USERNAME_PASSWORD_DISABLE Criteria: If the value mspub.exe is REG_DWORD = 1, this is not a finding.

Fix: F-45494r710618_fix

Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2010 (Machine) -> Security Settings -> IE Security "Disable user name and password" to "Enabled" and place a check in the "mspub.exe" check box.

b
Enabling IE Bind to Object functionality must be present.
SC-18 - Medium - CCI-001695 - V-242262 - SV-242262r960921_rule
RMF Control
SC-18
Severity
M
CCI
CCI-001695
Version
DTOO111 - Publisher
Vuln IDs
  • V-242262
  • V-17174
Rule IDs
  • SV-242262r960921_rule
  • SV-33890
Internet Explorer performs a number of safety checks before initializing an ActiveX control. It will not initialize a control if the kill bit for the control is set in the registry, or if the security settings for the zone in which the control is located do not allow it to be initialized. This functionality can be controlled separately for instances of Internet Explorer spawned by Office applications (for example, if a user clicks a link in an Office document or selects a menu option that loads a Web page). A security risk could occur if potentially dangerous controls are allowed to load.
Checks: C-45537r710620_chk

The policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2010 (Machine) -> Security Settings -> IE Security "Bind to Object" must be "Enabled" and a check in the "mspub.exe" check box must be present. Procedure: Use the Windows Registry Editor to navigate to the following key: HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_SAFE_BINDTOOBJECT Criteria: If the value mspub.exe is REG_DWORD = 1, this is not a finding.

Fix: F-45495r710621_fix

Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2010 (Machine) -> Security Settings -> IE Security "Bind to Object" to "Enabled" and place a check in the "mspub.exe" check box.

b
Saved from URL mark to assure Internet zone processing must be enforced.
SC-18 - Medium - CCI-001170 - V-242263 - SV-242263r961092_rule
RMF Control
SC-18
Severity
M
CCI
CCI-001170
Version
DTOO117 - Publisher
Vuln IDs
  • V-242263
  • V-17175
Rule IDs
  • SV-242263r961092_rule
  • SV-33919
Typically, when Internet Explorer loads a Web page from a Universal Naming Convention (UNC) share that contains a Mark of the Web (MOTW) comment, indicating the page was saved from a site on the Internet, Internet Explorer runs the page in the Internet security zone instead of the less restrictive Local Intranet security zone. This functionality can be controlled separately for instances of Internet Explorer spawned by Office applications (for example, if a user clicks a link in an Office document or selects a menu option that loads a Web page). If Internet Explorer does not evaluate the page for a MOTW, potentially dangerous code could be allowed to run.
Checks: C-45538r710623_chk

The policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2010 (Machine) -> Security Settings -> IE Security "Saved from URL" must be "Enabled" and a check in the "mspub.exe" check box must be present. Procedure: Use the Windows Registry Editor to navigate to the following key: HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_UNC_SAVEDFILECHECK Criteria: If the value mspub.exe is REG_DWORD = 1, this is not a finding.

Fix: F-45496r710624_fix

Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2010 (Machine) -> Security Settings -> IE Security "Saved from URL" to "Enabled" and place a check in the "mspub.exe" check box.

b
Navigation to URL's embedded in Office products must be blocked.
SC-18 - Medium - CCI-001170 - V-242264 - SV-242264r961092_rule
RMF Control
SC-18
Severity
M
CCI
CCI-001170
Version
DTOO123 - Publisher
Vuln IDs
  • V-242264
  • V-17183
Rule IDs
  • SV-242264r961092_rule
  • SV-33900
To protect users from attacks, Internet Explorer usually does not attempt to load malformed URLs. This functionality can be controlled separately for instances of Internet Explorer spawned by Office applications (for example, if a user clicks a link in an Office document or selects a menu option that loads a Web page). If Internet Explorer attempts to load a malformed URL, a security risk could occur in some cases.
Checks: C-45539r710626_chk

The policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2010 (Machine) -> Security Settings -> IE Security "Navigate URL" must be "Enabled" and a check in the "mspub.exe" check box must be present. Procedure: Use the Windows Registry Editor to navigate to the following key: HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_VALIDATE_NAVIGATE_URL Criteria: If the value mspub.exe is REG_DWORD = 1, this is not a finding.

Fix: F-45497r710627_fix

Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2010 (Machine) -> Security Settings -> IE Security "Navigate URL" to "Enabled" and place a check in the "mspub.exe" check box.

b
Scripted Window Security must be enforced.
SC-18 - Medium - CCI-001695 - V-242265 - SV-242265r960921_rule
RMF Control
SC-18
Severity
M
CCI
CCI-001695
Version
DTOO124 - Publisher
Vuln IDs
  • V-242265
  • V-26588
Rule IDs
  • SV-242265r960921_rule
  • SV-33922
Malicious websites often try to confuse or trick users into giving a site permission to perform an action allowing the site to take control of the users' computers in some manner. Disabling or not configuring this setting allows unknown websites to: -Create browser windows appearing to be from the local operating system. -Draw active windows displaying outside of the viewable areas of the screen capturing keyboard input. -Overlay parent windows with their own browser windows to hide important system information, choices or prompts.
Checks: C-45540r710629_chk

The policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2010 (Machine) -> Security Settings -> IE Security "Scripted Window Security Restrictions" must be set to "Enabled" and "mspub.exe" is checked. Procedure: Use the Windows Registry Editor to navigate to the following key: HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_WINDOW_RESTRICTIONS Criteria: If the value mspub.exe is REG_DWORD = 1, this is not a finding.

Fix: F-45498r710630_fix

Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2010 (Machine) -> Security Settings -> IE Security "Scripted Window Security Restrictions" to "Enabled" and "mspub.exe" is checked.

b
Add-on Management functionality must be allowed.
SC-18 - Medium - CCI-001662 - V-242266 - SV-242266r961086_rule
RMF Control
SC-18
Severity
M
CCI
CCI-001662
Version
DTOO126 - Publisher
Vuln IDs
  • V-242266
  • V-26584
Rule IDs
  • SV-242266r961086_rule
  • SV-33887
Internet Explorer add-ons are pieces of code, run in Internet Explorer, to provide additional functionality. Rogue add-ons may contain viruses or other malicious code. Disabling or not configuring this setting could allow malicious code or users to become active on user computers or the network. For example, a malicious user can monitor and then use keystrokes users type into Internet Explorer. Even legitimate add-ons may demand resources, compromising the performance of Internet Explorer, and the operating systems for user computers.
Checks: C-45541r710632_chk

The policy value for Computer Configuration -> Administrative Templates -> Microsoft Ofice 2010 (Machine) -> Security Settings -> IE Security "Add-on Management" must be set to "Enabled" and "mspub.exe" is checked. Procedure: Use the Windows Registry Editor to navigate to the following key: HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ADDON_MANAGEMENT Criteria: If the value mspub.exe is REG_DWORD = 1, this is not a finding.

Fix: F-45499r710633_fix

Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2010 (Machine) -> Security Settings -> IE Security "Add-on Management" to "Enabled" and "mspub.exe" is checked.

b
Application add-ins must be signed by Trusted Publisher.
CM-5 - Medium - CCI-001749 - V-242267 - SV-242267r960954_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001749
Version
DTOO127 - Publisher
Vuln IDs
  • V-242267
  • V-26589
Rule IDs
  • SV-242267r960954_rule
  • SV-33929
Office 2010 applications do not check the digital signature on application add-ins before opening them. Disabling or not configuring this setting may allow an application to load a dangerous add-in. As a result, malicious code could become active on user computers or the network.
Checks: C-45542r710635_chk

The policy value for User Configuration -> Administrative Templates -> Microsoft Publisher 2010 -> Security -> Trust Center "Require that application add-ins are signed by Trusted Publisher" must be set to "Enabled". Procedure: Use the Windows Registry Editor to navigate to the following key: HKCU\Software\Policies\Microsoft\Office\14.0\publisher\security Criteria: If the value RequireAddinSig is REG_DWORD = 1, this is not a finding.

Fix: F-45500r710636_fix

Set the policy value for User Configuration -> Administrative Templates -> Microsoft Publisher 2010 -> Security -> Trust Center "Require that application add-ins are signed by Trusted Publisher" to "Enabled".

b
Data Execution Prevention must be enforced.
SC-18 - Medium - CCI-001170 - V-242268 - SV-242268r961092_rule
RMF Control
SC-18
Severity
M
CCI
CCI-001170
Version
DTOO128 - Publisher
Vuln IDs
  • V-242268
  • V-26590
Rule IDs
  • SV-242268r961092_rule
  • SV-33926
Data Execution Prevention (DEP) is a set of hardware and software technologies performing additional checks on memory to help prevent malicious code from running on a system. The primary benefit of DEP is to help prevent code execution from data pages. Enabling this setting, turns off Data Execution Prevention. As a result, malicious code takes advantage of code injection or buffer overflow vulnerabilities possibly exploiting the computer.
Checks: C-45543r710638_chk

The policy value for User Configuration -> Administrative Templates -> Microsoft Publisher 2010 -> Security -> Trust Center "Turn off Data Execution Prevention" must be set to "Disabled". Procedure: Use the Windows Registry Editor to navigate to the following key: HKCU\Software\Policies\Microsoft\Office\14.0\publisher\security Criteria: If the value EnableDEP is REG_DWORD = 1, this is not a finding.

Fix: F-45501r710639_fix

Set the policy value for User Configuration -> Administrative Templates -> Microsoft Publisher 2010 -> Security -> Trust Center "Turn off Data Execution Prevention" to "Disabled".

b
Links that invoke instances of IE from within an Office product must be blocked.
SC-18 - Medium - CCI-001662 - V-242269 - SV-242269r961086_rule
RMF Control
SC-18
Severity
M
CCI
CCI-001662
Version
DTOO129 - Publisher
Vuln IDs
  • V-242269
  • V-17184
Rule IDs
  • SV-242269r961086_rule
  • SV-33894
The Pop-up Blocker feature in Internet Explorer can be used to block most unwanted pop-up and pop-under windows from appearing. This functionality can be controlled separately for instances of Internet Explorer spawned by 2007 Office applications (for example, if a user clicks a link in an Office document or selects a menu option that loads a Web page). If the Pop-up Blocker is disabled, disruptive and potentially dangerous pop-up windows could load and present a security risk.
Checks: C-45544r710641_chk

The policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2010 (Machine) -> Security Settings -> IE Security "Block popups" must be "Enabled" and "mspub.exe" is checked. Procedure: Use the Windows Registry Editor to navigate to the following key: HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_WEBOC_POPUPMANAGEMENT Criteria: If the value mspub.exe is REG_DWORD = 1, this is not a finding.

Fix: F-45502r710642_fix

Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2010 (Machine) -> Security Settings -> IE Security "Block popups" to "Enabled" and select "mspub.exe".

b
Trust Bar Notifications for unsigned application add-ins must be blocked.
CM-5 - Medium - CCI-001749 - V-242270 - SV-242270r960954_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001749
Version
DTOO131 - Publisher
Vuln IDs
  • V-242270
  • V-17187
Rule IDs
  • SV-242270r960954_rule
  • SV-33928
If an application is configured to require all add-ins be signed by a trusted publisher, any unsigned add-ins the application loads will be disabled and the application will display the Trust Bar at the top of the active window. The Trust Bar contains a message informing users about the unsigned add-in.
Checks: C-45545r710644_chk

The policy value for User Configuration -> Administrative Templates -> Microsoft Publisher 2010 -> Security -> Trust Center "Disable Trust Bar Notification for unsigned application add-ins" must be "Enabled". Procedure: Use the Windows Registry Editor to navigate to the following key: HKCU\Software\Policies\Microsoft\Office\14.0\publisher\security Criteria: If the value NoTBPromptUnsignedAddin is REG_DWORD = 1, this is not a finding.

Fix: F-45503r710645_fix

Set the policy value for User Configuration -> Administrative Templates -> Microsoft Publisher 2010 -> Security -> Trust Center "Disable Trust Bar Notification for unsigned application add-ins" to "Enabled".

b
File Downloads must be configured for proper restrictions.
SC-18 - Medium - CCI-001169 - V-242271 - SV-242271r961089_rule
RMF Control
SC-18
Severity
M
CCI
CCI-001169
Version
DTOO132 - Publisher
Vuln IDs
  • V-242271
  • V-26587
Rule IDs
  • SV-242271r961089_rule
  • SV-33916
Disabling this setting allows websites to present file download prompts via code without the user specifically initiating the download. User preferences may also allow the download to occur without prompting or interacting with the user. Even if Internet Explorer prompts the user to accept the download, some websites abuse this functionality. Malicious websites may continually prompt users to download a file or present confusing dialog boxes to trick users into downloading or running a file. If the download occurs and it contains malicious code, the code could become active on user computers or the network.
Checks: C-45546r710647_chk

The policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2010 (Machine) -> Security Settings -> IE Security "Restrict File Download" must be set to "Enabled" and "mspub.exe" is checked. Procedure: Use the Windows Registry Editor to navigate to the following key: HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_RESTRICT_FILEDOWNLOAD Criteria: If the value mspub.exe is REG_DWORD = 1, this is not a finding.

Fix: F-45504r710648_fix

Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2010 (Machine) -> Security Settings -> IE Security "Restrict File Download" to "Enabled" and "mspub.exe" is checked.

b
Protection from zone elevation must be enforced.
SC-18 - Medium - CCI-001695 - V-242272 - SV-242272r960921_rule
RMF Control
SC-18
Severity
M
CCI
CCI-001695
Version
DTOO209 - Publisher
Vuln IDs
  • V-242272
  • V-26585
Rule IDs
  • SV-242272r960921_rule
  • SV-33901
Internet Explorer places restrictions on each web page users can use the browser to open. Web pages on a user's local computer have the fewest security restrictions and reside in the Local Machine zone, making this security zone a prime target for malicious users and code. Disabling or not configuring this setting could allow pages in the Internet zone to navigate to pages in the Local Machine zone to then run code to elevate privileges. This could allow malicious code or users to become active on user computers or the network.
Checks: C-45547r710650_chk

The policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2010 (Machine) -> Security Settings -> IE Security "Protection From Zone Elevation" must be set to "Enabled" and "mspub.exe" is checked. Procedure: Use the Windows Registry Editor to navigate to the following key: HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ZONE_ELEVATION Criteria: If the value mspub.exe is REG_DWORD = 1, this is not a finding.

Fix: F-45505r710651_fix

Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2010 (Machine) -> Security Settings -> IE Security "Protection From Zone Elevation" to "Enabled" and "mspub.exe" is checked.

b
ActiveX Installs must be configured for proper restriction.
SC-18 - Medium - CCI-002460 - V-242273 - SV-242273r961779_rule
RMF Control
SC-18
Severity
M
CCI
CCI-002460
Version
DTOO211 - Publisher
Vuln IDs
  • V-242273
  • V-26586
Rule IDs
  • SV-242273r961779_rule
  • SV-33905
Microsoft ActiveX controls allow unmanaged, unprotected code to run on the user computers. ActiveX controls do not run within a protected container in the browser like the other types of HTML or Microsoft Silverlight-based controls. Disabling or not configuring this setting does not block prompts for ActiveX control installations and these prompts display to users. This could allow malicious code to become active on user computers or the network.
Checks: C-45548r710653_chk

The policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2010 (Machine) -> Security Settings -> IE Security "Restrict ActiveX Install" must be set to "Enabled" and "mspub.exe" is checked. Procedure: Use the Windows Registry Editor to navigate to the following key: HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_RESTRICT_ACTIVEXINSTALL Criteria: If the value mspub.exe is REG_DWORD = 1, this is not a finding.

Fix: F-45506r710654_fix

Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Office 2010 (Machine) -> Security Settings -> IE Security "Restrict ActiveX Install" to "Enabled" and "mspub.exe" is checked.

b
Warning Bar settings for VBA macros must be configured.
CM-7 - Medium - CCI-000381 - V-242274 - SV-242274r960963_rule
RMF Control
CM-7
Severity
M
CCI
CCI-000381
Version
DTOO304 - Publisher
Vuln IDs
  • V-242274
  • V-17545
Rule IDs
  • SV-242274r960963_rule
  • SV-33930
When users open files containing VBA Macros, applications open the files with the macros disabled and displays the Trust Bar with a warning that macros are present and have been disabled. Users may then enable these macros by clicking Options on the Trust Bar and selecting the option to enable them. Disabling or not configuring this setting may allow dangerous macros to become active on user computers or the network.
Checks: C-45549r710656_chk

The policy value for User Configuration -> Administrative Templates -> Microsoft Publisher 2010-> Security -> Trust Center "VBA Macro Notification Settings" must be "Enabled (Disabled all with notifications)". Procedure: Use the Windows Registry Editor to navigate to the following key: HKCU\Software\Policies\Microsoft\Office\14.0\publisher\security Criteria: If the value VBAWarnings is REG_DWORD = 2, this is not a finding.

Fix: F-45507r710657_fix

Set the policy value for User Configuration -> Administrative Templates -> Microsoft Publisher 2010-> Security -> Trust Center "VBA Macro Notification Settings" to "Enabled (Disabled all with notifications)".

b
Fatally corrupt files must be blocked from opening.
SC-18 - Medium - CCI-001662 - V-242275 - SV-242275r961086_rule
RMF Control
SC-18
Severity
M
CCI
CCI-001662
Version
DTOO322 - Publisher
Vuln IDs
  • V-242275
  • V-26707
Rule IDs
  • SV-242275r961086_rule
  • SV-34092
Enabling this setting allows user to open fatally corrupt Publisher 2010 files. As a result, malicious code or users could become active on user computers or the network. For example, a malicious user may purposely corrupt a Publisher file. The corrupted file could force the application to fail or execute malicious code, giving the malicious user control of Publisher 2010.
Checks: C-45550r710659_chk

The policy value for User Configuration -> Administrative Templates -> Microsoft Publisher 2010 -> Security "Prompt to allow fatally corrupt files to open instead of blocking them" must be set to "Disabled". Procedure: Use the Windows Registry Editor to navigate to the following key: HKCU\Software\Policies\Microsoft\Office\14.0\publisher Criteria: If the value PromptForBadFiles is REG_DWORD = 0, this is not a finding.

Fix: F-45508r710660_fix

Set the policy value for User Configuration -> Administrative Templates -> Microsoft Publisher 2010 -> Security "Prompt to allow fatally corrupt files to open instead of blocking them" to "Disabled".

b
The Publisher Automation Security Level must be configured for high security.
SC-18 - Medium - CCI-001170 - V-242276 - SV-242276r961092_rule
RMF Control
SC-18
Severity
M
CCI
CCI-001170
Version
DTOO323 - Publisher
Vuln IDs
  • V-242276
  • V-26708
Rule IDs
  • SV-242276r961092_rule
  • SV-34093
When a separate application is used to launch Publisher 2010 programmatically, any macros can run in the programmatically-opened application without being blocked. Disabling or not configuring this setting could allow a malicious user to use automation to run malicious code in Publisher 2010.
Checks: C-45551r710662_chk

The policy value for User Configuration -> Administrative Templates -> Microsoft Publisher 2010 -> Security "Publisher Automation Security Level" must be set to "Enabled and High (Disabled)" is selected. Procedure: Use the Windows Registry Editor to navigate to the following key: HKCU\Software\Policies\Microsoft\Office\Common\Security Criteria: If the value AutomationSecurityPublisher is REG_DWORD = 3, this is not a finding.

Fix: F-45509r710663_fix

Set the policy value for User Configuration -> Administrative Templates -> Microsoft Publisher 2010 -> Security "Publisher Automation Security Level" to "Enabled and High (Disabled)" is selected.

c
The version of Microsoft Publisher running on the system must be a supported version.
SI-2 - High - CCI-002605 - V-265898 - SV-265898r999898_rule
RMF Control
SI-2
Severity
H
CCI
CCI-002605
Version
DTOO999 - Publisher
Vuln IDs
  • V-265898
Rule IDs
  • SV-265898r999898_rule
Security flaws with software applications are discovered daily. Vendors are constantly updating and patching their products to address newly discovered security vulnerabilities. Organizations (including any contractor to the organization) are required to promptly install security-relevant software updates (e.g., patches, service packs, and hot fixes). Flaws discovered during security assessments, continuous monitoring, incident response activities, or information system error handling must also be addressed expeditiously. Organization-defined time periods for updating security-relevant software may vary based on a variety of factors including, for example, the security category of the information system or the criticality of the update (i.e., severity of the vulnerability related to the discovered flaw). This requirement will apply to software patch management solutions that are used to install patches across the enclave and also to applications themselves that are not part of that patch management solution. For example, many browsers today provide the capability to install their own patch software. Patch criticality, as well as system criticality will vary. Therefore, the tactical situations regarding the patch management process will also vary. This means that the time period used must be a configurable parameter. Time frames for application of security-relevant software updates may be dependent upon the Information Assurance Vulnerability Management (IAVM) process. The application will be configured to check for and install security-relevant software updates within an identified time period from the availability of the update. The specific time period will be defined by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs).
Checks: C-69817r999896_chk

Microsoft Publisher 2010 is no longer supported by the vendor. If the system is running Microsoft Publisher 2010, this is a finding.

Fix: F-69721r999897_fix

Upgrade to a supported version.