How long is September 17 2022 from now?

September 17 was 105 days ago.
Period: September 17th, 2022 and December 31st, 2022.

This date occurred 3 months and 14 days ago. Exactly 15 weeks have passed by since then.

Days: 105 Weeks: 15 Months: 3 Hours: 2,520

What day of the week was September 17?

September 17 fell on a Saturday, which is the weekend.

What happened on this day?

This might refresh your memory:

September 17th, 2022: Soccer: It is reported that Mathias Pogba has been charged with exorting his younger brother, Paul Pogba.

Other interesting facts.

Facts that highlight how long ago September 17 was.

In the past 105 day(s), the average American has used between 8,400 and 10,500 gallons of water.
The average person produced 462 pounds of trash in this period.
The "typical" Internet user spent around 735 hours of their time online.
215,753,424,600 tons of ice has melted.
If you quit smoking on September 17, you have now saved an estimated $659 USD.
The average American has dined out 89 times.

Other days.

October 17th 2022 was 75 days ago, it was 2 months and 14 days ago. October 17th 2022 was on a Monday and was in week 42 of 2022. It was the day number 290 of the year 2022.

How many years since October 17, 2022?
0 years

October 17th 2022 was 0 years ago.
How many months since October 17, 2022?
2 months
October 17th 2022 was 2 months ago.
How many weeks since October 17, 2022?
10 weeks
October 17th 2022 was 10 weeks ago.
How many days since October 17, 2022?
75 days
October 17th 2022 was 75 days ago.
How many hours since October 17, 2022?
1,800 hours
October 17th 2022 was 1,800 hours ago.
How many minutes since October 17, 2022?
108,000 minutes
October 17th 2022 was 108,000 minutes ago.
How many seconds since October 17, 2022?
6,480,000 seconds
October 17th 2022 was 6,480,000 seconds ago.
How many weekends since October 17, 2022?
10 weekends
There have been 10 weekends since October 17th 2022.
How many weekdays since October 17, 2022?
55 weekdays

There have been 55 weekdays since October 17th 2022.

Recent calculations

This website uses cookies to collect information about how you interact with our website. We use this information in order to improve and customize your browsing experience and for analytics and metrics about our visitors. To find out more about the cookies we use, see our Privacy Policy.

DateTime to DateSeptember 03, 2022-3 months and 29 daysSeptember 04, 2022-3 months and 28 daysSeptember 05, 2022-3 months and 27 daysSeptember 06, 2022-3 months and 26 daysSeptember 07, 2022-3 months and 25 daysSeptember 08, 2022-3 months and 24 daysSeptember 09, 2022-3 months and 23 daysSeptember 10, 2022-3 months and 22 daysSeptember 11, 2022-3 months and 21 daysSeptember 12, 2022-3 months and 20 daysSeptember 13, 2022-3 months and 19 daysSeptember 14, 2022-3 months and 18 daysSeptember 15, 2022-3 months and 17 daysSeptember 16, 2022-3 months and 16 daysSeptember 17, 2022-3 months and 15 daysSeptember 18, 2022-3 months and 14 daysSeptember 19, 2022-3 months and 13 daysSeptember 20, 2022-3 months and 12 daysSeptember 21, 2022-3 months and 11 daysSeptember 22, 2022-3 months and 10 daysSeptember 23, 2022-3 months and 9 daysSeptember 24, 2022-3 months and 8 daysSeptember 25, 2022-3 months and 7 daysSeptember 26, 2022-3 months and 6 daysSeptember 27, 2022-3 months and 5 daysSeptember 28, 2022-3 months and 4 daysSeptember 29, 2022-3 months and 3 daysSeptember 30, 2022-3 months and 2 daysOctober 01, 2022-3 months and 1 dayOctober 02, 2022-3 months

November 8, 2022 update – Microsoft released security updates for CVE-2022-41040 and CVE-2022-41082. We recommend that customers protect their organizations by applying the updates immediately to affected systems. The options described in the Mitigations section are no longer recommended. For more information, review the Exchange Team blog.

Summary

On November 8 Microsoft released security updates for two zero-day vulnerabilities affecting Microsoft Exchange Server 2013, Exchange Server 2016, and Exchange Server 2019. The first one, identified as CVE-2022-41040, is a Server-Side Request Forgery (SSRF) vulnerability, and the second one, identified as CVE-2022-41082, allows Remote Code Execution (RCE) when PowerShell is accessible to the attacker.

Currently, Microsoft is aware of limited targeted attacks using these two vulnerabilities. In these attacks, CVE-2022-41040 can enable an authenticated attacker to remotely trigger CVE-2022-41082. It should be noted that authenticated access to the vulnerable Exchange Server is necessary to successfully exploit either vulnerability.

Microsoft Security Threat Intelligence teams have provided further analysis of observed activity along with detection and hunting guidance in a Microsoft Security blog.

Mitigations

Exchange Online customers do not need to take any action.

We strongly recommend applying the Exchange Server updates for CVE-2022-41040 and CVE-2022-41082. The mitigations below are no longer recommended.

Previously, we recommended Exchange Server customers should complete both the URL Rewrite rule mitigation for CVE-2022-41040 and the Disable remote PowerShell for non-admins mitigation for CVE-2022-41082 described below.

URL Rewrite rule

The previous Exchange Server mitigation was to add a blocking rule in “IIS Manager -> Default Web Site -> URL Rewrite -> Actions” to block the known attack patterns.

Option 1: For customers who have the Exchange Emergency Mitigation Service (EEMS) enabled, Microsoft released the URL Rewrite mitigation for Exchange Server 2016 and Exchange Server 2019. The mitigation is enabled automatically and is updated to include the URL Rewrite rule improvements. Please see this blog post for more information on this service and how to check active mitigations.

Option 2: Microsoft created the EOMTv2 script for the URL Rewrite mitigation steps and updated it to include the URL Rewrite rule improvements. EOMTv2 script will auto-update on Internet connected machines and the updated version will show as 22.10.07.2029. The script should be re-run on any Exchange Server without EEMS enabled. https://aka.ms/EOMTv2

Option 3: Customers can follow the instructions below, which include the step 6 string update. A previously created rule for this mitigation can be deleted after the steps below are followed.

1. Open IIS Manager.
2. Select Default Web Site.
3. In the Feature View, click URL Rewrite.

4. In the Actions pane on the right-hand side, click Add Rule(s)…

5. Select Request Blocking and click OK.

6. Add the string “(?=.*autodiscover)(?=.*powershell)” (excluding quotes).
7. Select Regular Expression under Using.
8. Select Abort Request under How to block and then click OK.

9. Expand the rule and select the rule with the pattern: (?=.*autodiscover)(?=.*powershell) and click Edit under Conditions.

10. Change the Condition input from {URL} to {UrlDecode:{REQUEST_URI}} and then click OK.

NOTE: If you need to change any rule it is best to delete and recreate it.

Impact: There is no known effect on Exchange functionality if URL Rewrite is installed as recommended.

Disable remote PowerShell access for non-admins

Previously, we strongly recommended Exchange Server customers disable remote PowerShell access for non-admin users in your organization to mitigate one of the vulnerabilities. While this is not necessary with the application of released updates, you may choose to do this to disable protocols that might not be in use. Guidance on how to do this for single user or multiple users is available here.

Detection and advanced hunting

For detection and advanced hunting guidance, customers should reference Analyzing attacks using the Exchange vulnerabilities CVE-2022-41040 and CVE-2022-41082.