Category Archives: Advisories

USN-5785-1: FreeRADIUS vulnerabilities

Read Time:36 Second

It was discovered that FreeRADIUS incorrectly handled multiple EAP-pwd
handshakes. An attacker could possibly use this issue to cause a denial of
service. This issue only affected Ubuntu 18.04 LTS. (CVE-2019-17185)

Shane Guan discovered that FreeRADIUS incorrectly handled memory when
checking unknown SIM option sent by EAP-SIM supplicant. An attacker could
possibly use this issue to cause a denial of service on the server. This
issue only affected Ubuntu 16.04 ESM, Ubuntu 18.04 LTS and Ubuntu 20.04
LTS. (CVE-2022-41860)

It was discovered that FreeRADIUS incorrectly handled memory when
processing certain abinary attributes. An attacker could possibly use this
issue to cause a denial of service on the server. (CVE-2022-41861)

Read More

CVE-2014-125039

Read Time:20 Second

A vulnerability, which was classified as problematic, has been found in kkokko NeoXplora. Affected by this issue is some unknown functionality of the component Trainer Handler. The manipulation leads to cross site scripting. The attack may be launched remotely. The name of the patch is dce1aecd6ee050a29f953ffd8f02f21c7c13f1e6. It is recommended to apply a patch to fix this issue. The identifier of this vulnerability is VDB-217352.

Read More

CVE-2010-10003

Read Time:19 Second

A vulnerability classified as critical was found in gesellix titlelink. Affected by this vulnerability is an unknown functionality of the file plugin_content_title.php. The manipulation of the argument phrase leads to sql injection. The name of the patch is b4604e523853965fa981a4e79aef4b554a535db0. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-217351.

Read More

Multiple Vulnerabilities in Google Android OS Could Allow for Arbitrary Code Execution

Read Time:25 Second

Multiple vulnerabilities have been discovered in Google Android OS, the most severe of which could allow for arbitrary code execution. Android is an operating system developed by Google for mobile devices, including, but not limited to, smartphones, tablets, and watches. Successful exploitation of the most severe of these vulnerabilities could allow for arbitrary code execution. Depending on the privileges associated with the exploited component, an attacker could then install programs; view, change, or delete data; or create new accounts with full rights.

Read More

python2.7-2.7.18-28.fc38

Read Time:18 Second

FEDORA-2023-01b481a31e

Packages in this update:

python2.7-2.7.18-28.fc38

Update description:

Automatic update for python2.7-2.7.18-28.fc38.

Changelog

* Mon Dec 19 2022 Charalampos Stratakis <cstratak@redhat.com> – 2.7.18-28
– Security fix for CVE-2022-45061: CPU denial of service via inefficient IDNA decoder
Related: rhbz#2144072

Read More

New Exploit Method Bypasses Official ProxyNotShell Mitigation

Read Time:2 Minute, 49 Second

FortiGuard Labs is aware of reports that threat actors are using a combination of ProxyNotShell vulnerabilities (CVE-2022-41040 and CVE-2022-41082) in combination with Outlook Web Access (OWA) and a server side request forgery (SSRF) in a new exploit chain utilizing PowerShell to obtain a foothold and deliver malware (tools, Play ransomware) within a targeted environment ultimately for persistence. The new exploit vector is a Server Side Request Forgery (SSRF) attack on Outlook Web Access (OWA) which is being dubbed as OWASSRF. According to Microsoft, the URL rewrite mitigations published on September 29 for organizations that have not patched are no longer recommended.ProxyNotShell OverviewEarlier in September, Microsoft disclosed two new 0-day vulnerabilities affecting Microsoft Exchange Server 2013, Exchange Server 2016, and Exchange Server 2019. They are:CVE-2022-41040 – a server-side request forgery (SSRF) vulnerability (CVSS 8.8)CVE-2022-41082 – allows for remote code execution (RCE) when Exchange PowerShell is accessible to the attacker (CVSS 8.8)Note:Although patches were released for CVE-2022-41040 and CVE-2022-41082, in November 2022, and will prevent successful exploitation; mitigation for organizations that have not patched are susceptible to this new attack vector.On a positive note and alleviating fears for organizations – the impact is lessened as attackers will need to have advanced knowledge of Exchange server credentials to the victim’s environment to successfully exploit this new vector.FortiGuard Labs recently published an Outbreak Alert and a blog for ProxyNotShell. See the Appendix for links to “Outbreak Alert: Microsoft Exchange ProxyNotShell Vulnerabilities” and “Microsoft Exchange 0-Day Vulnerability Updates”Why is this Significant?Although Microsoft released patches in November 2022, the two vulnerabilities (CVE-2022-41040 and CVE-2022-41082) are chained together and used in conjunction with Outlook Web Access in a SSRF attack bypassing previous recommended mitigation. Microsoft Exchange servers that are patched are believed to be not vulnerable. How Widespread Are Attacks?Because the exploit chain requires attackers to obtain credentials of compromised Exchange accounts beforehand; attacks are limited to targeted attacks.Has the Vendor Released a Patch for CVE-2022-41040 and CVE-2022-41082?Yes, Microsoft released a patch on November 8, 2022, as part of the regular Microsoft Patch Tuesday cycle.What is Play Ransomware?Play is a relatively new ransomware that was first detected in June 2022. Play ransomware encrypts files on victims’ machines and adds a “.play” extension to them. The ransomware adopted the double-extortion methodology of encrypting endpoints and/or other infrastructure of value within an organization and then threatening to release exfiltrated data from those machines on the internet if a ransom is not paid.Play ransomware is covered in a recent Ransomware Roundup blog. For details, see the Appendix for a link to “Ransomware Roundup – Play Ransomware”.Any Recommended Mitigation?FortiGuard Labs recommends that all organizations apply the latest patches from the November 2022 Exchange Server Security Update to avoid any possible compromise to the OWASSRF vector. Microsoft no longer recommends URL rewrite mitigation for those not patched. Also, it is suggested that system administrators disable remote PowerShell for non admin users where possible.What is the Status of Protection?Customers running the latest definitions are protected against known ProxyNotShell attempts by the following IPS signatures:MS.Exchange.Server.OWA.Remote.Code.Execution (CVE-2022-41080)MS.Exchange.Server.Autodiscover.Remote.Code.Execution (CVE-2022-41082)

Read More