{"id":5441,"date":"2020-06-10T17:17:24","date_gmt":"2020-06-10T16:17:24","guid":{"rendered":"https:\/\/www.n-able.com\/?p=5441"},"modified":"2022-06-10T18:19:03","modified_gmt":"2022-06-10T17:19:03","slug":"june-2020-patch-tuesday-update-highest-cve-count-history","status":"publish","type":"post","link":"https:\/\/www.n-able.com\/de\/blog\/june-2020-patch-tuesday-update-highest-cve-count-history","title":{"rendered":"June 2020 Patch Tuesday Update\u2014Highest CVE count in history"},"content":{"rendered":"

The June patch Tuesday release is another heavy one, meaning the research community keeps finding more vulnerabilities and Microsoft continues to step up and knock them down. In total, 128 unique CVE numbers were fixed\u2014the highest so far. Of those, 11 are marked \u201cCritical\u201d across operating systems, browsers, and one in SharePoint. There are also some very notable \u201cImportant\u201d vulnerabilities to pay attention to, which we\u2019ll break down here as well. There are no \u201cExploit Detected\u201d entries this month but there are some \u201cExploitation More Likely\u201d listings\u2014including a few surprises (I\u2019m talking about you SMBv1!). As always, let\u2019s start with the \u201cCriticals.\u201d<\/p>\n

Operating systems<\/b><\/h3>\n

There are five \u201cCritical\u201d operating system vulnerabilities in this batch. They\u2019re all remote code execution vulnerabilities, and all are listed as \u201cExploitation Less Likely.\u201d This is usually due to the complexity required to deliver and exploit the vulnerability.<\/p>\n

CVE-2020-1248<\/a>\u00a0is a GDI+ remote code execution vulnerability that would give the attacker the same rights as the logged-on user. It requires a user to access a malicious webpage or to open a document sent via email or file sharing to execute the vulnerability. The fix addresses how Graphics Device Interface handles memory. This vulnerability affects the most recent versions of Windows 10 (1903, 1909, and the newly released 2004) and the corresponding Server Core systems. The vulnerability is only listed as \u201cImportant\u201d on version 2004, which means there were likely some changes in that area of the code in version 2004 that mitigate the risk.<\/p>\n

The next one,\u00a0CVE-2020-1281<\/a>, is a vulnerability in Object Linking (OLE) that would allow an attacker to execute code on a system if a user accesses a file or program on that system. This vulnerability affects all supported versions of Windows, including Windows 7 and Server 2008, all the way up to the most recent versions of Windows 10 and Windows Server (including Core). This means you will need ESU to update Windows 7 and Server 2008.<\/p>\n

There is a Windows Shell file path validation issue that would allow an attacker to execute code with the same permissions as the user.\u00a0CVE-2020-1286<\/a>\u00a0fixes this vulnerability in Windows 10 (version 1709 up to 2004, including corresponding Server versions).<\/p>\n

CVE-2020-1299<\/a>\u00a0would also grant the attacker the same rights as the logged-on user if they were to click on a malicious .LNK file in a remote share or removable drive. This patch addresses how the shortcut is processed.<\/p>\n

Finally,\u00a0CVE-2020-1300<\/a>\u00a0is a vulnerability in Windows that would allow an attacker to execute remote code if the user opened a cabinet file on the affected system.<\/p>\n

Browsers<\/b><\/h3>\n

It seems this month that Microsoft has more concern with the browser-based vulnerabilities, as several of them are marked \u201cExploitation More Likely.\u201d First up is a trio of VBScript remote code execution vulnerabilities in Internet Explorer.<\/p>\n

CVE-2020-1260<\/a>,\u00a0CVE-2020-1213<\/a>, and\u00a0CVE-2020-1216<\/a>\u00a0have identical descriptions and exploitability assessments. Accessing a malicious website or an ActiveX control in Microsoft 365 that uses the IE engine for rendering could grant the attacker the same rights as the user. They all affect Internet Explorer 11 on all supported operating systems, and Internet Explorer 9 on Server 2008 systems. As with most browser vulnerabilities, they are rated as Moderate on the Server operating systems because of the enhanced security configuration that browsers come configured with when installed on Server.<\/p>\n

CVE-2020-1219<\/a>\u00a0is a browser memory corruption vulnerability in Internet Explorer 11, as well as the Edge-HTML version of the Edge Browser. It would also grant the attacker the same rights as the user and is marked as \u201cExploitation More Likely.\u201d<\/p>\n

The final \u201cCritical\u201d browser vulnerability is marked as \u201cExploitation Less Likely.\u201d CVE-2020-1073 is a scripting engine memory corruption vulnerability and affects the Edge-HTML version of Microsoft Edge on Windows 10 1709 up to 1909 (including Server versions).<\/p>\n

Other applications<\/b><\/h3>\n

The final \u201cCritical\u201d affects SharePoint Server.\u00a0CVE-2020-1181<\/a>\u00a0is a remote code execution vulnerability. If an attacker has access, they could create a specially crafted page on SharePoint 2010 SP2, SharePoint Foundation 2013 SP1, SharePoint Enterprise 2016, or SharePoint Server 2019.<\/p>\n

Finally, Microsoft released an advisory for Adobe products,\u00a0ADV200010<\/a>\u00a0for Adobe Flash components in Windows 8.1 up to current versions of Windows 10. IT should be noted that this is a separate update from the cumulative updates and should be given attention.<\/p>\n

Other notable issues<\/b><\/h3>\n

We often direct our focus to the \u201cCritical\u201d updates, but sometimes you can find some updates of concern in the \u201cImportant\u201d vulnerabilities as well. If you\u2019re prioritizing only certain types of updates, you should consider adding \u201cImportant\u201d to your criteria, as there are sometimes some hidden \u201chigh-risk\u201d vulnerabilities in that group. There are a few of note we will discuss here:<\/p>\n

CVE-2020-1301<\/a>\u00a0is a Windows SMB remote code execution vulnerability, and it\u2019s listed as \u201cExploitation More Likely.\u201d It affects SMBv1 in all supported operating systems from Windows 7 up to Windows 10 current version (2004) and all corresponding server versions. If this sounds familiar, it\u2019s a vulnerability in the same area the famous\u00a0ShadowBrokers<\/a>\u00a0mass-released exploits for in 2017, and was the vector for the WannaCry and NotPetya attacks that year. This vulnerability doesn\u2019t quite meet that level of risk though\u2014mainly because this one requires authentication, while WannaCry did not. It\u2019s important to note that even Microsoft recommends you disable SMBv1, as the protocol is 30 years old and most communications and applications have moved to SMBv2 or v3 by now. If you have SMBv1 enabled, you should disable it immediately, as this will likely not be the end of vulnerabilities found in the protocol.\u00a0 If you cannot disable it, you should deploy updates immediately. The instructions on how to disable it are included in the Workarounds section of the\u00a0article<\/a>.<\/p>\n

CVE-2020-1241<\/a>\u00a0is also listed as \u201cExploitation More Likely.\u201d It\u2019s a vulnerability in the kernel that would allow an attacker to bypass security but requires access to the affected system. This fact gives this vulnerability a lower CVSS score, but clearly Microsoft suspects bad actors may attempt to leverage this vulnerability in the future. Windows 10 from 1607 to 2004 (including Server versions) are affected by this vulnerability.<\/p>\n

CVE-2020-1247<\/a>\u00a0and\u00a0CVE-2020-1251\u00a0<\/a>\u00a0are both Windows kernel-mode driver vulnerabilities that would require an attacker to log on to the affected system, but Microsoft has also listed this one as \u201cExploitation More Likely.\u201d CVE-22020-1247 affects all versions of Windows from Windows 7 to current (including Server), while CVE-2020-1251 affects Windows 8.1 to current versions of Windows 10.<\/p>\n

The final \u201cImportant\u201d vulnerability listed as \u201cExploitation More Likely\u201d is found in Internet Explorer 11 on all supported operating systems.\u00a0CVE-2020-1230<\/a>\u00a0would grant the attacker the same rights as the user if they accessed a malicious webpage or opened a document in Office where the IE rendering engine was used.<\/p>\n

27 Vulnerabilities were fixed in Windows 7 based operating systems\u2014falling under the Extended Security Updates (ESU) required to continue getting fixes. If you\u2019re running this operating system, we recommend you purchase ESU or upgrade to a supported operating system.<\/p>\n

Summary<\/b><\/h3>\n

From a priority standpoint, browsers and internet-facing workstations should take priority and then SharePoint. If you haven\u2019t disabled SMBv1 yet across your systems, you should do that this month. The good news: since version 1709 of Windows 10, Microsoft hasn\u2019t installed SMBv1 by default on a new installation. However, you could have installed and enabled it yourself. If you\u2019re running Windows 7, this is another good reason to move to a supported (and more secure) operating system.<\/p>\n

Remember, if you\u2019re running Windows 10 or the corresponding server operating system, the Cumulative update will contain all the fixes for the operating system and the browsers. Older operating systems require you either install the updates separately or install the Rollups.<\/p>\n

It\u2019s another \u201cheavy\u201d month of vulnerabilities in the world of Windows, so make sure you\u2019re up to date. When looking at the themes for attack vectors in all the vulnerabilities we\u2019ve discussed, I keep coming back to one point: since it can take time to deploy patches across an IT estate, it\u2019s always important to ensure other layers of protection are in place. For example, many of the vulnerabilities mention email as a vector but your email security solution shouldn\u2019t allow attachments such as .LNK and .CAB files. Limiting access to malicious websites with web protection reduces the risk of an attempted exploit. Disabling SMBv1 greatly reduces the risk of a successful attack. Combining these with a timely patch deployment plan helps ensure you\u2019re protecting yourself and your customers.<\/p>\n

Let\u2019s stay safe out there!<\/p>\n

Gill Langston is head security nerd for SolarWinds MSP. You can follow Gill on Twitter at\u00a0@cybersec_nerd<\/a><\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

The June patch Tuesday release is another heavy one, meaning the research community keeps finding more vulnerabilities and Microsoft continues to step up and knock them down. In total, 128…<\/p>\n","protected":false},"author":27,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"class_list":["post-5441","post","type-post","status-publish","format-standard","hentry","topic-head-nerds","topic-patch-management","topic-security"],"acf":[],"yoast_head":"\nJune 2020 Patch Tuesday Update\u2014Highest CVE count in history - N-able<\/title>\n<meta name=\"description\" content=\"As the research community keeps finding more vulnerabilities Microsoft continues to step up and knock them down. Gill Langston takes a look at the latest Patch Tuesday \u2013 another heavy one.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.n-able.com\/de\/blog\/june-2020-patch-tuesday-update-highest-cve-count-history\" \/>\n<meta property=\"og:locale\" content=\"de_DE\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"June 2020 Patch Tuesday Update\u2014Highest CVE count in history - N-able\" \/>\n<meta property=\"og:description\" content=\"As the research community keeps finding more vulnerabilities Microsoft continues to step up and knock them down. Gill Langston takes a look at the latest Patch Tuesday \u2013 another heavy one.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.n-able.com\/de\/blog\/june-2020-patch-tuesday-update-highest-cve-count-history\" \/>\n<meta property=\"og:site_name\" content=\"N-able\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/NableMSP\" \/>\n<meta property=\"article:published_time\" content=\"2020-06-10T16:17:24+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-06-10T17:19:03+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.n-able.com\/wp-content\/uploads\/2021\/03\/share-image.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"630\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Gill Langston\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@Nable\" \/>\n<meta name=\"twitter:site\" content=\"@Nable\" \/>\n<meta name=\"twitter:label1\" content=\"Verfasst von\" \/>\n\t<meta name=\"twitter:data1\" content=\"Gill Langston\" \/>\n\t<meta name=\"twitter:label2\" content=\"Gesch\u00e4tzte Lesezeit\" \/>\n\t<meta name=\"twitter:data2\" content=\"7\u00a0Minuten\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.n-able.com\/de\/blog\/june-2020-patch-tuesday-update-highest-cve-count-history#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.n-able.com\/de\/blog\/june-2020-patch-tuesday-update-highest-cve-count-history\"},\"author\":{\"name\":\"Gill Langston\",\"@id\":\"https:\/\/www.n-able.com\/de#\/schema\/person\/ccb02e43837727da6ab962f5357e872a\"},\"headline\":\"June 2020 Patch Tuesday Update\u2014Highest CVE count in history\",\"datePublished\":\"2020-06-10T17:17:24+01:00\",\"dateModified\":\"2022-06-10T17:19:03+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.n-able.com\/de\/blog\/june-2020-patch-tuesday-update-highest-cve-count-history\"},\"wordCount\":1437,\"publisher\":{\"@id\":\"https:\/\/www.n-able.com\/de#organization\"},\"articleSection\":[\"Head Nerds\",\"Patch Management\",\"Security\"],\"inLanguage\":\"de\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.n-able.com\/de\/blog\/june-2020-patch-tuesday-update-highest-cve-count-history\",\"url\":\"https:\/\/www.n-able.com\/de\/blog\/june-2020-patch-tuesday-update-highest-cve-count-history\",\"name\":\"June 2020 Patch Tuesday Update\u2014Highest CVE count in history - N-able\",\"isPartOf\":{\"@id\":\"https:\/\/www.n-able.com\/de#website\"},\"datePublished\":\"2020-06-10T17:17:24+01:00\",\"dateModified\":\"2022-06-10T17:19:03+00:00\",\"description\":\"As the research community keeps finding more vulnerabilities Microsoft continues to step up and knock them down. Gill Langston takes a look at the latest Patch Tuesday \u2013 another heavy one.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.n-able.com\/de\/blog\/june-2020-patch-tuesday-update-highest-cve-count-history#breadcrumb\"},\"inLanguage\":\"de\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.n-able.com\/de\/blog\/june-2020-patch-tuesday-update-highest-cve-count-history\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.n-able.com\/de\/blog\/june-2020-patch-tuesday-update-highest-cve-count-history#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Security\",\"item\":\"https:\/\/www.n-able.com\/de\/blog\/category\/security\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"June 2020 Patch Tuesday Update\u2014Highest CVE count in history\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.n-able.com\/de#website\",\"url\":\"https:\/\/www.n-able.com\/de\",\"name\":\"N-able\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/www.n-able.com\/de#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.n-able.com\/de?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"de\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.n-able.com\/de#organization\",\"name\":\"N-able\",\"url\":\"https:\/\/www.n-able.com\/de\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"de\",\"@id\":\"https:\/\/www.n-able.com\/de#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.n-able.com\/wp-content\/uploads\/2021\/02\/logo-n-able-vertical-dark.svg\",\"contentUrl\":\"https:\/\/www.n-able.com\/wp-content\/uploads\/2021\/02\/logo-n-able-vertical-dark.svg\",\"width\":\"1024\",\"height\":\"1024\",\"caption\":\"N-able\"},\"image\":{\"@id\":\"https:\/\/www.n-able.com\/de#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.facebook.com\/NableMSP\",\"https:\/\/x.com\/Nable\",\"https:\/\/www.linkedin.com\/company\/n-able\",\"https:\/\/www.youtube.com\/channel\/UClnp77HHg4aME-S-3fWQhFw\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.n-able.com\/de#\/schema\/person\/ccb02e43837727da6ab962f5357e872a\",\"name\":\"Gill Langston\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"de\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/7e3211da194e6f8c74fccea7140d31255418759757a5d157a8eb4fd12fd0f1f2?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/7e3211da194e6f8c74fccea7140d31255418759757a5d157a8eb4fd12fd0f1f2?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/7e3211da194e6f8c74fccea7140d31255418759757a5d157a8eb4fd12fd0f1f2?s=96&d=mm&r=g\",\"caption\":\"Gill Langston\"}}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"June 2020 Patch Tuesday Update\u2014Highest CVE count in history - N-able","description":"As the research community keeps finding more vulnerabilities Microsoft continues to step up and knock them down. Gill Langston takes a look at the latest Patch Tuesday \u2013 another heavy one.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.n-able.com\/de\/blog\/june-2020-patch-tuesday-update-highest-cve-count-history","og_locale":"de_DE","og_type":"article","og_title":"June 2020 Patch Tuesday Update\u2014Highest CVE count in history - N-able","og_description":"As the research community keeps finding more vulnerabilities Microsoft continues to step up and knock them down. Gill Langston takes a look at the latest Patch Tuesday \u2013 another heavy one.","og_url":"https:\/\/www.n-able.com\/de\/blog\/june-2020-patch-tuesday-update-highest-cve-count-history","og_site_name":"N-able","article_publisher":"https:\/\/www.facebook.com\/NableMSP","article_published_time":"2020-06-10T16:17:24+00:00","article_modified_time":"2022-06-10T17:19:03+00:00","og_image":[{"width":1200,"height":630,"url":"https:\/\/www.n-able.com\/wp-content\/uploads\/2021\/03\/share-image.jpg","type":"image\/jpeg"}],"author":"Gill Langston","twitter_card":"summary_large_image","twitter_creator":"@Nable","twitter_site":"@Nable","twitter_misc":{"Verfasst von":"Gill Langston","Gesch\u00e4tzte Lesezeit":"7\u00a0Minuten"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.n-able.com\/de\/blog\/june-2020-patch-tuesday-update-highest-cve-count-history#article","isPartOf":{"@id":"https:\/\/www.n-able.com\/de\/blog\/june-2020-patch-tuesday-update-highest-cve-count-history"},"author":{"name":"Gill Langston","@id":"https:\/\/www.n-able.com\/de#\/schema\/person\/ccb02e43837727da6ab962f5357e872a"},"headline":"June 2020 Patch Tuesday Update\u2014Highest CVE count in history","datePublished":"2020-06-10T17:17:24+01:00","dateModified":"2022-06-10T17:19:03+00:00","mainEntityOfPage":{"@id":"https:\/\/www.n-able.com\/de\/blog\/june-2020-patch-tuesday-update-highest-cve-count-history"},"wordCount":1437,"publisher":{"@id":"https:\/\/www.n-able.com\/de#organization"},"articleSection":["Head Nerds","Patch Management","Security"],"inLanguage":"de"},{"@type":"WebPage","@id":"https:\/\/www.n-able.com\/de\/blog\/june-2020-patch-tuesday-update-highest-cve-count-history","url":"https:\/\/www.n-able.com\/de\/blog\/june-2020-patch-tuesday-update-highest-cve-count-history","name":"June 2020 Patch Tuesday Update\u2014Highest CVE count in history - N-able","isPartOf":{"@id":"https:\/\/www.n-able.com\/de#website"},"datePublished":"2020-06-10T17:17:24+01:00","dateModified":"2022-06-10T17:19:03+00:00","description":"As the research community keeps finding more vulnerabilities Microsoft continues to step up and knock them down. Gill Langston takes a look at the latest Patch Tuesday \u2013 another heavy one.","breadcrumb":{"@id":"https:\/\/www.n-able.com\/de\/blog\/june-2020-patch-tuesday-update-highest-cve-count-history#breadcrumb"},"inLanguage":"de","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.n-able.com\/de\/blog\/june-2020-patch-tuesday-update-highest-cve-count-history"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.n-able.com\/de\/blog\/june-2020-patch-tuesday-update-highest-cve-count-history#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Security","item":"https:\/\/www.n-able.com\/de\/blog\/category\/security"},{"@type":"ListItem","position":2,"name":"June 2020 Patch Tuesday Update\u2014Highest CVE count in history"}]},{"@type":"WebSite","@id":"https:\/\/www.n-able.com\/de#website","url":"https:\/\/www.n-able.com\/de","name":"N-able","description":"","publisher":{"@id":"https:\/\/www.n-able.com\/de#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.n-able.com\/de?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"de"},{"@type":"Organization","@id":"https:\/\/www.n-able.com\/de#organization","name":"N-able","url":"https:\/\/www.n-able.com\/de","logo":{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/www.n-able.com\/de#\/schema\/logo\/image\/","url":"https:\/\/www.n-able.com\/wp-content\/uploads\/2021\/02\/logo-n-able-vertical-dark.svg","contentUrl":"https:\/\/www.n-able.com\/wp-content\/uploads\/2021\/02\/logo-n-able-vertical-dark.svg","width":"1024","height":"1024","caption":"N-able"},"image":{"@id":"https:\/\/www.n-able.com\/de#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/NableMSP","https:\/\/x.com\/Nable","https:\/\/www.linkedin.com\/company\/n-able","https:\/\/www.youtube.com\/channel\/UClnp77HHg4aME-S-3fWQhFw"]},{"@type":"Person","@id":"https:\/\/www.n-able.com\/de#\/schema\/person\/ccb02e43837727da6ab962f5357e872a","name":"Gill Langston","image":{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/secure.gravatar.com\/avatar\/7e3211da194e6f8c74fccea7140d31255418759757a5d157a8eb4fd12fd0f1f2?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/7e3211da194e6f8c74fccea7140d31255418759757a5d157a8eb4fd12fd0f1f2?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/7e3211da194e6f8c74fccea7140d31255418759757a5d157a8eb4fd12fd0f1f2?s=96&d=mm&r=g","caption":"Gill Langston"}}]}},"_links":{"self":[{"href":"https:\/\/www.n-able.com\/de\/wp-json\/wp\/v2\/posts\/5441","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.n-able.com\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.n-able.com\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.n-able.com\/de\/wp-json\/wp\/v2\/users\/27"}],"replies":[{"embeddable":true,"href":"https:\/\/www.n-able.com\/de\/wp-json\/wp\/v2\/comments?post=5441"}],"version-history":[{"count":0,"href":"https:\/\/www.n-able.com\/de\/wp-json\/wp\/v2\/posts\/5441\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.n-able.com\/de\/wp-json\/wp\/v2\/media?parent=5441"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}