Skip to content

Commit 77056bc

Browse files
authored
Merge pull request #8427 from bhuney/CM_MSRC
ConfigMgr MSRC article draft
2 parents 0d494a4 + 9c89a29 commit 77056bc

3 files changed

Lines changed: 89 additions & 0 deletions

File tree

Lines changed: 77 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,77 @@
1+
---
2+
title: NTLM connection fallback update for Microsoft Endpoint Configuration Manager
3+
titleSuffix: Configuration Manager
4+
description: NTLM connection fallback update for Configuration Manager
5+
ms.date: 09/20/2022
6+
ms.prod: configuration-manager
7+
ms.technology: configmgr-core
8+
ms.topic: reference
9+
ms.assetid: 3c93a332-e818-46fe-860f-cbebf4dd9ab3
10+
author: bhuney
11+
ms.author: brianhun
12+
manager: dougeby
13+
---
14+
# NTLM connection fallback update for Microsoft Endpoint Configuration Manager
15+
16+
*Applies to: Configuration Manager (current branch, versions 2103, 2107, 2111, 2203, 2207)*
17+
18+
## Summary of KB15498768
19+
Disabling the **Allow connection fallback to NTLM** option in *Client Push Installation Properties* is not honored under either of the following conditions:
20+
- If there are Kerberos authentication failures the client push account will attempt an NTLM connection instead.
21+
- The site server computer account will attempt a connection using NTLM if Kerberos authentication fails for all defined client push installation accounts.
22+
23+
This update prevents any attempt at NTLM authentication for client push installation when the **Allow connection fallback to NTLM** option is disabled.
24+
25+
Installation of this update resolves the following security issue:
26+
- [CVE-2022-37972](https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2022-37972)
27+
28+
Beginning with Configuration Manager current branch, version 2207, the **Allow connection fallback to NTLM** option is *disabled* by default on new site installations.
29+
30+
It is recommended to disable this option in existing environments, where possible, to increase security.
31+
32+
Refer to the following documents for more detail on client and NTLM security:
33+
- [Security and privacy for Configuration Manager clients](../../core/clients/deploy/plan/security-and-privacy-for-clients.md#security-guidance-for-clients)
34+
- [KB5005413: Mitigating NTLM Relay Attacks on Active Directory Certificate Services](https://support.microsoft.com/topic/kb5005413-mitigating-ntlm-relay-attacks-on-active-directory-certificate-services-ad-cs-3612b773-4043-4aa9-b23d-b87910cd3429)
35+
- [Network security: Restrict NTLM: Outgoing NTLM traffic to remote servers](https://learn.microsoft.com/windows/security/threat-protection/security-policy-settings/network-security-restrict-ntlm-outgoing-ntlm-traffic-to-remote-servers)
36+
37+
Environments using versions of Configuration Manager current branch prior to 2103 are encouraged to update to a later supported version. Administrators can also disable use of automatic and manual client push installation methods to remove the risk of exposure to this issue.
38+
For more information, see [Support for Configuration Manager current branch versions](../../core/servers/manage/current-branch-versions-supported.md).
39+
40+
## Update information for Microsoft Endpoint Configuration Manager, versions 2103-2207
41+
An update to resolve this issue is available in the **Updates and Servicing** node of the Configuration Manager console for environments that have versions 2103-2207 installed.
42+
43+
#### Update replacement information
44+
This update does not replace any previously released updates.
45+
46+
#### Restart information
47+
For Configuration Manager versions 2107 and later, this update does not require a computer restart or a [site reset](../../core/servers/manage/modify-your-infrastructure.md#bkmk_reset) after installation.
48+
49+
Configuration Manager version 2103 will require a site reset after update installation.
50+
51+
### Additional installation information
52+
After you install this update on a primary site, pre-existing secondary sites must be manually updated. To update a secondary site in the Configuration Manager console, select **Administration** > **Site Configuration** > **Sites** > **Recover Secondary Site**, and then select the secondary site. The primary site then reinstalls that secondary site by using the updated files. Configurations and settings for the secondary site are not affected by this reinstallation. The new, upgraded, and reinstalled secondary sites under that primary site automatically receive this update.
53+
54+
Run the following SQL Server command on the site database to check whether the update version of a secondary site matches that of its parent primary site:
55+
```sql
56+
select dbo.fnGetSecondarySiteCMUpdateStatus ('SiteCode_of_secondary_site')
57+
```
58+
If the value 1 is returned, the site is up to date, with all the hotfixes applied on its parent primary site.
59+
60+
If the value 0 is returned, the site has not installed all the fixes that are applied to the primary site, and you should use the **Recover Secondary Site** option to update the secondary site.
61+
62+
## Version information
63+
No major components are updated with this release.
64+
65+
## File information
66+
File information is available in the following version-specific file lists (KB15498768_FileList.txt):
67+
- [Configuration Manager 2103](https://aka.ms/KB15498768_2103_FileList)
68+
- [Configuration Manager 2107](https://aka.ms/KB15498768_2107_FileList)
69+
- [Configuration Manager 2111](https://aka.ms/KB15498768_2111_FileList)
70+
- [Configuration Manager 2203](https://aka.ms/KB15498768_2203_FileList)
71+
- [Configuration Manager 2207](https://aka.ms/KB15498768_2207_FileList)
72+
73+
## Release history
74+
- September 20, 2022: Initial hotfix release
75+
76+
## References
77+
[Updates and servicing for Configuration Manager](../../core/servers/manage/updates.md)

memdocs/configmgr/hotfix/TOC.yml

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,8 @@ items:
99
href: 2207/14959905.md
1010
- name: KB 14978429 Connected cache update for Microsoft Endpoint Configuration Manager version 2207
1111
href: 2207/14978429.md
12+
- name: KB 15498768 NTLM connection fallback update
13+
href: 2207/15498768.md
1214
- name: Version 2203
1315
items:
1416
- name: KB 13174460 Summary of changes in 2203
@@ -19,6 +21,8 @@ items:
1921
href: 2203/14480034.md
2022
- name: KB 14244456 Update rollup for Microsoft Endpoint Configuration Manager version 2203
2123
href: 2203/14244456.md
24+
- name: KB 15498768 NTLM connection fallback update
25+
href: 2207/15498768.md
2226
- name: Version 2111
2327
items:
2428
- name: KB 10096997 Summary of changes in 2111
@@ -31,6 +35,8 @@ items:
3135
href: 2111/12819689.md
3236
- name: KB 12896009 Update rollup for Microsoft Endpoint Configuration Manager version 2111
3337
href: 2111/12896009.md
38+
- name: KB 15498768 NTLM connection fallback update
39+
href: 2207/15498768.md
3440
- name: Version 2107
3541
items:
3642
- name: KB 10096997 Summary of changes in 2107
@@ -41,6 +47,8 @@ items:
4147
href: 2107/11121541.md
4248
- name: KB 12636660 Network access account update
4349
href: 2107/12636660.md
50+
- name: KB 15498768 NTLM connection fallback update
51+
href: 2207/15498768.md
4452
- name: Version 2103
4553
items:
4654
- name: KB 9210721 Summary of changes in 2103
@@ -59,6 +67,8 @@ items:
5967
href: 2103/10589155.md
6068
- name: KB 10582136 Tenant attach update
6169
href: 2103/10582136.md
70+
- name: KB 15498768 NTLM connection fallback update
71+
href: 2207/15498768.md
6272
- name: Version 2010
6373
items:
6474
- name: KB 4599442 Summary of changes in 2010

memdocs/configmgr/hotfix/index.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,8 @@ landingContent:
2525
url: 2207/14840616.md
2626
- text: KB 14959905 Early update ring
2727
url: 2207/14959905.md
28+
- text: KB 15498768 NTLM connection fallback update
29+
url: 2207/15498768.md
2830

2931
- title: Configuration Manager 2203
3032
linkLists:

0 commit comments

Comments
 (0)