DEF CON 28 Safe Mode IoT Village – Parker Wiksell’s ‘Vulnerability Trends In The Supply Chain’

Many thanks to DEF CON and Conference Speakers for publishing their outstanding presentations; of which, originally appeared at the organization’s DEFCON 28 SAFE MODE Conference, and on the DEF CON YouTube channel. Enjoy!

Permalink

The post DEF CON 28 Safe Mode IoT Village – Parker Wiksell’s ‘Vulnerability Trends In The Supply Chain’ appeared first on Security Boulevard.

Read More

The post DEF CON 28 Safe Mode IoT Village – Parker Wiksell’s ‘Vulnerability Trends In The Supply Chain’ appeared first on Malware Devil.

https://malwaredevil.com/2021/01/22/def-con-28-safe-mode-iot-village-parker-wiksells-vulnerability-trends-in-the-supply-chain/?utm_source=rss&utm_medium=rss&utm_campaign=def-con-28-safe-mode-iot-village-parker-wiksells-vulnerability-trends-in-the-supply-chain

FBI to Investigate Parler, New Russian Host will be Revoked

A House committee has tasked the FBI to review Parler. Follow the money.

The post FBI to Investigate Parler, New Russian Host will be Revoked appeared first on Security Boulevard.

Read More

The post FBI to Investigate Parler, New Russian Host will be Revoked appeared first on Malware Devil.

https://malwaredevil.com/2021/01/22/fbi-to-investigate-parler-new-russian-host-will-be-revoked/?utm_source=rss&utm_medium=rss&utm_campaign=fbi-to-investigate-parler-new-russian-host-will-be-revoked

In the Pandemic Era, Proof Digital Identity with Continuous Authentication & Behavioral Biometrics

This past November at the 2020 ISMG Virtual Cybersecurity & Fraud Summit in Washington D.C., I presented on how organizations can make digital identity both user-friendly and near-impenetrable. My session, Proofing Digital Identity with Continuous Authentication & Behavioral Biometrics considered how behavioral biometrics offers a better balancing-act between security, privacy, compliance, and user experience. Throughout …

Continue reading “In the Pandemic Era, Proof Digital Identity with Continuous Authentication & Behavioral Biometrics”

The post In the Pandemic Era, Proof Digital Identity with Continuous Authentication & Behavioral Biometrics appeared first on BehavioSec.

The post In the Pandemic Era, Proof Digital Identity with Continuous Authentication & Behavioral Biometrics appeared first on Security Boulevard.

Read More

The post In the Pandemic Era, Proof Digital Identity with Continuous Authentication & Behavioral Biometrics appeared first on Malware Devil.

https://malwaredevil.com/2021/01/22/in-the-pandemic-era-proof-digital-identity-with-continuous-authentication-behavioral-biometrics/?utm_source=rss&utm_medium=rss&utm_campaign=in-the-pandemic-era-proof-digital-identity-with-continuous-authentication-behavioral-biometrics

Discord-Stealing Malware Invades npm Packages

The CursedGrabber malware has infiltrated the open-source software code repository.
Read More

The post Discord-Stealing Malware Invades npm Packages appeared first on Malware Devil.

https://malwaredevil.com/2021/01/22/discord-stealing-malware-invades-npm-packages/?utm_source=rss&utm_medium=rss&utm_campaign=discord-stealing-malware-invades-npm-packages

From Google Cloud Blog: “New whitepaper: Designing and deploying a data security strategy with…

From Google Cloud Blog: “New whitepaper: Designing and deploying a data security strategy with Google Cloud”

Here is another very fun resource we created (jointly with Andrew Lance from Sidechain), a paper on designing and running data security strategy on Google Cloud.

• Read our launch blog here — a long excerpt is quoted below.
• Read Sidechain blog here — look for a useful data security migration checklist.
• Read the paper here[PDF]

— —

William Gibson said it best: “The future is already here — it’s just not evenly distributed.”

The cloud has arrived. Data security in the cloud is too often a novel problem for our customers. Well-worn paths to security are lacking. We often see customers struggling to adapt their data security posture to this new reality. There is an understanding that data security is critical, but a lack of well understood principles to drive an effective data security program. Thus, we are excited to share a view of how to deploy a modern and effective data security program.

Today, we are releasing a new white paper “Designing and deploying a data security strategy with Google Cloud” that accomplishes exactly that. It was written jointly by Andrew Lance of Sidechain (Sidechain blog post about this paper) and Dr. Anton Chuvakin, with a fair amount of help from other Googlers, of course.

Before we share some of our favorite quotes from the paper, let me spend a few more minutes explaining the vision behind it.

Specifically, we wanted to explore both the question of starting a data security program in a cloud-native way, as well as adjusting your existing daily security program when you start utilizing cloud computing.

Imagine you are migrating to the cloud and you are a traditional company. You have some data security capabilities, and most likely you have an existing daily security program, part of your overall security program. Perhaps you are deploying tools like DLP, encryption, data classification and possibly others. Suddenly, or perhaps not so suddenly, you’re migrating some of your data processing and some of your data to the cloud. What to do? Do my controls still work? Are my practices current? Am I looking at the right threats? How do I marry my cloud migration effort and my other daily security effort? Our paper seeks to address this scenario by giving you advice on the strategy, complete with Google Cloud examples.

On the other hand, perhaps you are the company that was born in the cloud. In this case, you may not have an existing data security effort. However, if you plan to process sensitive or regulated data in the cloud, you need to create one. How does a cloud native data security program look like? Which of the lessons learned by others on premise I can ignore? What are some of the cloud-native ways for securing the data?

As a quick final comment, the paper does not address the inclusion of privacy requirements. It is a worthwhile and valuable goal, just not the one we touched in the paper.

Here are some of our favorite quotes from the paper:

• “Simply applying a data security strategy designed for on-premise workloads isn’t adequate [for the cloud]. It lacks the ability to address cloud-specific requirements and doesn’t take advantage of the great amount of [cloud] security services and capabilities”
• A solid cloud data security strategy should rely on three pillars: “Identity / Access Boundaries / Visibility” (the last item covers the spectrum of assessment, detection, investigation and other monitoring and observability needs)
• Useful questions to ponder include ”How does my data security strategy need to change to accommodate a shift to the cloud? What new security challenges for data protection do I need to be aware of in the cloud? What does my cloud provider offer that could streamline or replace my on-premise controls?”
• “You will invariably need to confront data security requirements in your journey to the cloud, and performing a “lift and shift” for your data security program won’t work to address the unique opportunities and challenges the cloud offers.”
• “As your organization moves its infrastructure and operations to the cloud, shift your data protection strategies to cloud-native thinking.”

[read the rest at GCP blog]

Enjoy the paper!

---

From Google Cloud Blog: “New whitepaper: Designing and deploying a data security strategy with… was originally published in Anton on Security on Medium, where people are continuing the conversation by highlighting and responding to this story.

The post From Google Cloud Blog: “New whitepaper: Designing and deploying a data security strategy with… appeared first on Security Boulevard.

Read More

The post From Google Cloud Blog: “New whitepaper: Designing and deploying a data security strategy with… appeared first on Malware Devil.

https://malwaredevil.com/2021/01/22/from-google-cloud-blog-new-whitepaper-designing-and-deploying-a-data-security-strategy-with/?utm_source=rss&utm_medium=rss&utm_campaign=from-google-cloud-blog-new-whitepaper-designing-and-deploying-a-data-security-strategy-with

Chrome wants to make your passwords stronger

A common sentiment, shared by many people down the years, is that storing passwords in browsers is a bad idea. Malware, for example, would specifically target password storage in browsers and plunder everything in sight.

Password managers weren’t exactly flying off the shelves back in 2007, your only real options were home grown. People ended up saving logins in all sorts of odd places: Text files, email accounts…you name it. Naturally, security-minded folks gravitated towards saving passwords in browsers, because what else were they going to do?

The browser password wars

Even just 8 years ago, it was still a hotly contested debate. The problem then was that passwords were stored in plain text. They aren’t now, but if the device you’re using is compromised it doesn’t matter. Malware files can decrypt your passwords, or wait for you to do it. So, no matter how recently you look, many of the same threats still exist for browser passwords. And new ones emerge, like the rogue advertisers trying to grab autofill data.

Let’s be clear: things are better now for passwords in browsers than they used to be. Even something as basic as having to enter your Windows password to view or copy saved passwords is reassuring. Making use of encryption, instead of leaving data lying around in plaintext, is excellent. Browsers taking things one step beyond simply storing, and checking for stolen passwords is great. Real time phishing protection is the icing on an ever-growing cake.

With that in mind, Chrome continues to make inroads in the name of beefing up browser password safety.

Weak password? Chrome 88 can help

Beginning with Chrome version 88, you can now check for weak passwords (open Settings and search for “Passwords”) and alter them on the fly, with just a few clicks. The “Change password” button doesn’t alter anything inside the browser, which may disappoint. It simply takes you to the site where you use that feeble password. At this point, you’ll have to manually alter the details. The browser should then detect you’ve altered the password and update its password database, as it normally would.

If you really want to know what the stored password is but can’t remember it, you’ll need your Windows login, as mentioned earlier.

There’s not a huge amount to add about this new feature, as it is indeed incredibly simple to use. A list of all your potentially weak passwords is displayed, and off you go to fix them all. This is to its benefit. It’s easy to get bogged down in password minutiae and end up not bothering.

You don’t need bells and whistles while looking for weak passwords. You just want a list of sites, and to be told where there’s a problem. In this regard, the new functionality more than delivers.

Browser or password manager?

Having said all of that…you may still wish to ignore all the above and stick with a dedicated password manager. No matter what password features are added to browsers, some folks will never want anything to do with that. There are a wealth of choices available. Totally offline, or online functionality: the choice really is yours. I’d be surprised if there isn’t something for everyone in the options available. But if you really don’t want a password manager, then browsers are a better solution than nothing at all.

Do you prefer to keep all your tools in the browser basket, or cast passwords away into dedicated password managers? Either way, we wish you many years of secure password management to come.

The post Chrome wants to make your passwords stronger appeared first on Malware Devil.

https://malwaredevil.com/2021/01/22/chrome-wants-to-make-your-passwords-stronger-2/?utm_source=rss&utm_medium=rss&utm_campaign=chrome-wants-to-make-your-passwords-stronger-2

Chrome wants to make your passwords stronger

A common sentiment, shared by many people down the years, is that storing passwords in browsers is a bad idea. Malware, for example, would specifically target password storage in browsers and plunder everything in sight.

Password managers weren’t exactly flying off the shelves back in 2007, your only real options were home grown. People ended up saving logins in all sorts of odd places: Text files, email accounts…you name it. Naturally, security-minded folks gravitated towards saving passwords in browsers, because what else were they going to do?

The browser password wars

Even just 8 years ago, it was still a hotly contested debate. The problem then was that passwords were stored in plain text. They aren’t now, but if the device you’re using is compromised it doesn’t matter. Malware files can decrypt your passwords, or wait for you to do it. So, no matter how recently you look, many of the same threats still exist for browser passwords. And new ones emerge, like the rogue advertisers trying to grab autofill data.

Let’s be clear: things are better now for passwords in browsers than they used to be. Even something as basic as having to enter your Windows password to view or copy saved passwords is reassuring. Making use of encryption, instead of leaving data lying around in plaintext, is excellent. Browsers taking things one step beyond simply storing, and checking for stolen passwords is great. Real time phishing protection is the icing on an ever-growing cake.

With that in mind, Chrome continues to make inroads in the name of beefing up browser password safety.

Weak password? Chrome 88 can help

Beginning with Chrome version 88, you can now check for weak passwords (open Settings and search for “Passwords”) and alter them on the fly, with just a few clicks. The “Change password” button doesn’t alter anything inside the browser, which may disappoint. It simply takes you to the site where you use that feeble password. At this point, you’ll have to manually alter the details. The browser should then detect you’ve altered the password and update its password database, as it normally would.

If you really want to know what the stored password is but can’t remember it, you’ll need your Windows login, as mentioned earlier.

There’s not a huge amount to add about this new feature, as it is indeed incredibly simple to use. A list of all your potentially weak passwords is displayed, and off you go to fix them all. This is to its benefit. It’s easy to get bogged down in password minutiae and end up not bothering.

You don’t need bells and whistles while looking for weak passwords. You just want a list of sites, and to be told where there’s a problem. In this regard, the new functionality more than delivers.

Browser or password manager?

Having said all of that…you may still wish to ignore all the above and stick with a dedicated password manager. No matter what password features are added to browsers, some folks will never want anything to do with that. There are a wealth of choices available. Totally offline, or online functionality: the choice really is yours. I’d be surprised if there isn’t something for everyone in the options available. But if you really don’t want a password manager, then browsers are a better solution than nothing at all.

Do you prefer to keep all your tools in the browser basket, or cast passwords away into dedicated password managers? Either way, we wish you many years of secure password management to come.

The post Chrome wants to make your passwords stronger appeared first on Malwarebytes Labs.

The post Chrome wants to make your passwords stronger appeared first on Malware Devil.

https://malwaredevil.com/2021/01/22/chrome-wants-to-make-your-passwords-stronger/?utm_source=rss&utm_medium=rss&utm_campaign=chrome-wants-to-make-your-passwords-stronger

Joy Of Tech® ‘After Trump’

via the Comic Noggins of Nitrozac and Snaggy at The Joy of Tech®!

Permalink

The post Joy Of Tech® ‘After Trump’ appeared first on Security Boulevard.

Read More

The post Joy Of Tech® ‘After Trump’ appeared first on Malware Devil.

https://malwaredevil.com/2021/01/22/joy-of-tech-after-trump/?utm_source=rss&utm_medium=rss&utm_campaign=joy-of-tech-after-trump

ESB-2020.4547.2 – UPDATE [Appliance] BIG-IP and BIG-IQ products: Multiple vulnerabilities

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

===========================================================================
             AUSCERT External Security Bulletin Redistribution

                              ESB-2020.4547.2
             Linux kernel and TMM vulnerability CVE-2020-25705
                              22 January 2021

===========================================================================

        AusCERT Security Bulletin Summary
        ---------------------------------

Product:           BIG-IP
                   BIG-IQ
Publisher:         F5 Networks
Operating System:  Network Appliance
Impact/Access:     Denial of Service        -- Existing Account      
                   Access Confidential Data -- Remote/Unauthenticated
                   Reduced Security         -- Remote/Unauthenticated
Resolution:        Mitigation
CVE Names:         CVE-2020-25705 CVE-2018-10675 

Reference:         ESB-2020.4505
                   ESB-2020.4391
                   ESB-2020.4377
                   ESB-2020.4375

Original Bulletin: 
   https://support.f5.com/csp/article/K09604370
   https://support.f5.com/csp/article/K40540405

Comment: This bulletin contains two (2) F5 Networks security advisories.

Revision History:  January  22 2021: K09604370 - Vendor added additional vulnerable component
                   December 24 2020: Initial Release

- --------------------------BEGIN INCLUDED TEXT--------------------

K09604370: Linux kernel and TMM vulnerability CVE-2020-25705

Original Publication Date: 24 Dec, 2020
Latest   Publication Date: 22 Jan, 2021

Security Advisory Description

A flaw in the way reply ICMP packets are limited in the Linux kernel
functionality was found that allows to quickly scan open UDP ports. This flaw
allows an off-path remote user to effectively bypassing source port UDP
randomization. The highest threat from this vulnerability is to confidentiality
and possibly integrity, because software that relies on UDP source port
randomization are indirectly affected as well. Kernel versions before 5.10 may
be vulnerable to this issue. (CVE-2020-25705)

Impact

A remote off-path attacker can determine open User Datagram Protocol (UDP)
source ports on a vulnerable system based on Internet Control Message Protocol
(ICMP) error messages, making it possible to execute a "SAD DNS attack."

Security Advisory Status

F5 Product Development has assigned ID 974093 (BIG-IP-control plane), ID 982697
(BIG-IP-data plane) and ID 974093-4 (BIG-IQ) to this vulnerability.

To determine if your product and version have been evaluated for this
vulnerability, refer to the Applies to (see versions) box. To determine if your
release is known to be vulnerable, the components or features that are affected
by the vulnerability, and for information about releases, point releases, or
hotfixes that address the vulnerability, refer to the following table. For more
information about security advisory versioning, refer to K51812227:
Understanding security advisory versioning.

+--------------+------+----------+----------+----------+------+---------------+
|              |      |Versions  |Fixes     |          |CVSSv3|Vulnerable     |
|Product       |Branch|known to  |introduced|Severity  |score^|component or   |
|              |      |be        |in        |          |1     |feature        |
|              |      |vulnerable|          |          |      |               |
+--------------+------+----------+----------+----------+------+---------------+
|              |16.x  |None      |Not       |          |      |               |
|              |      |          |applicable|          |      |               |
|              +------+----------+----------+          |      |               |
|              |15.x  |None      |Not       |          |      |               |
|BIG-IP (LTM,  |      |          |applicable|          |      |               |
|AAM, Advanced +------+----------+----------+          |      |               |
|WAF, AFM,     |14.x  |None      |Not       |          |      |Linux kernel   |
|Analytics,    |      |          |applicable|          |      |(control       |
|APM, ASM,     +------+----------+----------+High      |7.4   |plane): ICMP   |
|DDHD, DNS,    |13.x  |13.1.0 -  |None      |          |      |implementation |
|FPS, GTM, Link|      |13.1.3    |          |          |      |               |
|Controller,   +------+----------+----------+          |      |               |
|PEM, SSLO)    |12.x  |12.1.0 -  |None      |          |      |               |
|              |      |12.1.5    |          |          |      |               |
|              +------+----------+----------+          |      |               |
|              |11.x  |11.6.1 -  |None      |          |      |               |
|              |      |11.6.5    |          |          |      |               |
+--------------+------+----------+----------+----------+------+---------------+
|              |16.x  |16.0.0 -  |None      |          |      |               |
|              |      |16.0.1    |          |          |      |               |
|              +------+----------+----------+          |      |               |
|              |15.x  |15.1.0 -  |None      |          |      |               |
|BIG-IP (LTM,  |      |15.1.2    |          |          |      |               |
|AAM, Advanced +------+----------+----------+          |      |               |
|WAF, AFM,     |14.x  |14.1.0 -  |None      |          |      |               |
|Analytics,    |      |14.1.3    |          |          |      |TMM^2 (data    |
|APM, ASM,     +------+----------+----------+High      |7.4   |plane): ICMP   |
|DDHD, DNS,    |13.x  |13.1.0 -  |None      |          |      |implementation |
|FPS, GTM, Link|      |13.1.3    |          |          |      |               |
|Controller,   +------+----------+----------+          |      |               |
|PEM, SSLO)    |12.x  |12.1.0 -  |None      |          |      |               |
|              |      |12.1.5    |          |          |      |               |
|              +------+----------+----------+          |      |               |
|              |11.x  |11.6.1 -  |None      |          |      |               |
|              |      |11.6.5    |          |          |      |               |
+--------------+------+----------+----------+----------+------+---------------+
|              |7.x   |7.0.0 -   |None      |          |      |               |
|              |      |7.1.0     |          |          |      |               |
|BIG-IQ        +------+----------+----------+          |      |Linux kernel   |
|Centralized   |6.x   |6.0.0 -   |None      |High      |7.4   |and TMM (ICMP  |
|Management    |      |6.1.0     |          |          |      |implementation)|
|              +------+----------+----------+          |      |               |
|              |5.x   |5.4.0     |None      |          |      |               |
+--------------+------+----------+----------+----------+------+---------------+
|Traffix SDC   |5.x   |None      |Not       |Not       |None  |None           |
|              |      |          |applicable|vulnerable|      |               |
+--------------+------+----------+----------+----------+------+---------------+

^1The CVSSv3 score link takes you to a resource outside of AskF5, and it is
possible that the document may be removed without our knowledge.

^2The Traffic Management Microkernel (TMM)

Security Advisory Recommended Actions

If you are running a version listed in the Versions known to be vulnerable
column, you can eliminate this vulnerability by upgrading to a version listed
in the Fixes introduced in column. If the table lists only an older version
than what you are currently running, or does not list a non-vulnerable version,
then no upgrade candidate currently exists.

Mitigation

  o BIG-IP control plane: Block outgoing ICMP port unreachable messages on the
    management interface
  o BIG-IP data plane: Lower the ICMP rate limit on TMM interfaces
       Configure the maximum reject rate
       Configure the ICMP error rate

BIG-IP control plane: Block outgoing ICMP port unreachable messages on the
management interface

To mitigate this vulnerability on the management interface, you can block
outgoing ICMP port unreachable messages. To do so, perform the following
procedure:

Impact of action: The impact of blocking ICMP packets depends on your specific
environment. F5 recommends testing any such changes during a maintenance window
with consideration to the possible impact on your specific environment.

 1. Log in to the BIG-IP command line.
 2. Block outgoing ICMP port unreachable messages by entering the following
    command:

    iptables -A OUTPUT -p icmp --icmp-type destination-unreachable -j DROP

 3. Create a backup of the /config/startup file by entering the following
    command:

    cp /config/startup /config/startup.backup

 4. Using a text editor, edit the /config/startup file.
 5. To ensure iptables changes persist across a reboot, add the following lines
    at the end of the file:

    # For CVE-2020-25705 described in K09604370
    #
    iptables -A OUTPUT -p icmp --icmp-type destination-unreachable -j DROP
    #

 6. Save the /config/startup file and exit the editor.

BIG-IP data plane: Lower the ICMP rate limit on TMM interfaces

To mitigate this vulnerability on the Traffic Management Microkernel (TMM)
interfaces, you can lower the ICMP rate limit. Adjust to a lower value to
lessen the possibility of the vulnerability being exploited, but ensure it is
still acceptable based on your environment and conditions. To do so, perform
the following procedure:

Configure the maximum reject rate

The tm.maxrejectrate database key allows you to adjust the number of TCP RST
packets or ICMP unreachable packets that the BIG-IP system sends in response to
incoming client-side or server-side packets that cannot be matched with
existing connections to BIG-IP virtual servers, self IP addresses, or secure
network address translations (SNATs). The default value for the
tm.maxrejectrate key is 250 TCP RSTs or 250 ICMP unreachable packets per
second. The minimum value allowed is 1 and the maximum value is 1000.

To adjust the rate at which the BIG-IP system issues TCP RSTs or ICMP
unreachable packets, perform the following procedure:

Impact of action: The impact of lowering the rate limit of ICMP packets depends
on your specific environment. F5 recommends testing any such changes during a
maintenance window with consideration to the possible impact on your specific
environment.

 1. Log in to the TMOS Shell (tmsh) by entering the following command:

    tmsh

 2. Adjust the tm.maxrejectrate database key by using the following command
    syntax:

    modify sys db tm.maxrejectrate value 

    For example, to change tm.maxrejectrate to 50, enter the following command:

    modify sys db tm.maxrejectrate value 50

Configure the ICMP error rate

The tm.maxicmprate BigDB key allows you to limit the number of responses the
BIG-IP LTM system sends for ICMP errors. The default value for the 
tm.maxicmprate BigDB key is 100.

To adjust the number of ICMP error responses from a BIG-IP system, perform the
following procedure:

Impact of action: The impact of lowering the rate limit of ICMP packets depends
on your specific environment. F5 recommends testing any such changes during a
maintenance window with consideration to the possible impact on your specific
environment.

 1. Log in to tmsh by entering the following command:

    tmsh

 2. Adjust the tm.maxicmprate database key by using the following command
    syntax:

    modify /sys db tm.maxicmprate value 

    For example, to change tm.maxicmprate to 50, enter the following command:

    modify sys db tm.maxicmprate value 50

 3. If the tm.maxforwardicmprate database key is not set to the default value
    of 0, lower the value by using the previous command syntax replacing
    tm.maxicmprate with tm.maxforwardicmprate.

Supplemental Information

o K13151: Configuring the rate at which the BIG-IP system issues TCP RSTs or
    ICMP unreachable packets
  o K14813: Detecting and mitigating DoS/DDoS attacks (11.4.x - 16.x)
  o K41942608: Overview of security advisory articles
  o K4602: Overview of the F5 security vulnerability response policy
  o K4918: Overview of the F5 critical issue hotfix policy
  o K9502: BIG-IP hotfix and point release matrix
  o K13123: Managing BIG-IP product hotfixes (11.x - 16.x)
  o K15106: Managing BIG-IQ product hotfixes
  o K15113: BIG-IQ hotfix and point release matrix
  o K167: Downloading software and firmware from F5
  o K9970: Subscribing to email notifications regarding F5 products
  o K9957: Creating a custom RSS feed to view new and updated documents

- --------------------------------------------------------------------------------

K40540405: Linux kernel vulnerability CVE-2018-10675

Original Publication Date: 24 Dec, 2020

Security Advisory Description

The do_get_mempolicy function in mm/mempolicy.c in the Linux kernel before
4.12.9 allows local users to cause a denial of service (use-after-free) or
possibly have unspecified other impact via crafted system calls. (
CVE-2018-10675)

Impact

A local attacker can cause a denial-of-service (DoS) or other negative impacts
on a vulnerable system.

Security Advisory Status

F5 Product Development has assigned ID 976181 (BIG-IP), ID 976409 (BIG-IQ),
and CPF-25230 (Traffix SDC) to this vulnerability.

To determine if your product and version have been evaluated for this
vulnerability, refer to the Applies to (see versions) box. To determine if your
release is known to be vulnerable, the components or features that are affected
by the vulnerability, and for information about releases, point releases, or
hotfixes that address the vulnerability, refer to the following table. For more
information about security advisory versioning, refer to K51812227:
Understanding security advisory versioning.

+---------------------+------+----------+----------+--------+------+----------+
|                     |      |Versions  |Fixes     |        |CVSSv3|Vulnerable|
|Product              |Branch|known to  |introduced|Severity|score^|component |
|                     |      |be        |in        |        |1     |or feature|
|                     |      |vulnerable|          |        |      |          |
+---------------------+------+----------+----------+--------+------+----------+
|                     |16.x  |None      |Not       |        |      |          |
|                     |      |          |applicable|        |      |          |
|                     +------+----------+----------+        |      |          |
|                     |15.x  |None      |Not       |        |      |          |
|                     |      |          |applicable|        |      |          |
|BIG-IP (LTM, AAM,    +------+----------+----------+        |      |          |
|Advanced WAF, AFM,   |14.x  |None      |Not       |        |      |          |
|Analytics, APM, ASM, |      |          |applicable|        |      |Linux     |
|DDHD, DNS, FPS, GTM, +------+----------+----------+Medium  |5.5   |kernel    |
|Link Controller, PEM,|13.x  |None      |Not       |        |      |          |
|SSLO)                |      |          |applicable|        |      |          |
|                     +------+----------+----------+        |      |          |
|                     |12.x  |12.1.0 -  |None      |        |      |          |
|                     |      |12.1.5    |          |        |      |          |
|                     +------+----------+----------+        |      |          |
|                     |11.x  |11.6.1 -  |None      |        |      |          |
|                     |      |11.6.5    |          |        |      |          |
+---------------------+------+----------+----------+--------+------+----------+
|                     |7.x   |7.0.0 -   |None      |        |      |          |
|                     |      |7.1.0     |          |        |      |          |
|BIG-IQ Centralized   +------+----------+----------+        |      |Linux     |
|Management           |6.x   |6.0.0 -   |None      |Medium  |5.5   |kernel    |
|                     |      |6.1.0     |          |        |      |          |
|                     +------+----------+----------+        |      |          |
|                     |5.x   |5.4.0     |None      |        |      |          |
+---------------------+------+----------+----------+--------+------+----------+
|Traffix SDC          |5.x   |5.1.0     |5.1.0 CF  |Medium  |5.5   |Linux     |
|                     |      |          |22        |        |      |kernel    |
+---------------------+------+----------+----------+--------+------+----------+

^1The CVSSv3 score link takes you to a resource outside of AskF5, and it is
possible that the document may be removed without our knowledge.

Security Advisory Recommended Actions

If you are running a version listed in the Versions known to be vulnerable
column, you can eliminate this vulnerability by upgrading to a version listed
in the Fixes introduced in column. If the table lists only an older version
than what you are currently running, or does not list a non-vulnerable version,
then no upgrade candidate currently exists.

Mitigation

To mitigate this vulnerability, you should permit management access to F5
products only over a secure network and restrict command line access for
affected systems to only trusted users. For more information about this
mitigation that is applicable to the BIG-IP system, refer to K13309:
Restricting access to the Configuration utility by source IP address (11.x -
16.x) and K13092: Overview of securing access to the BIG-IP system.

Supplemental Information

o K41942608: Overview of security advisory articles
  o K4602: Overview of the F5 security vulnerability response policy
  o K4918: Overview of the F5 critical issue hotfix policy
  o K9502: BIG-IP hotfix and point release matrix
  o K13123: Managing BIG-IP product hotfixes (11.x - 16.x)
  o K15106: Managing BIG-IQ product hotfixes
  o K15113: BIG-IQ hotfix and point release matrix
  o K167: Downloading software and firmware from F5
  o K9970: Subscribing to email notifications regarding F5 products
  o K9957: Creating a custom RSS feed to view new and updated documents

- --------------------------END INCLUDED TEXT--------------------

You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.

NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members.  As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.

NOTE: This is only the original release of the security bulletin.  It may
not be updated when updates to the original are made.  If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.

Contact information for the authors of the original document is included
in the Security Bulletin above.  If you have any questions or need further
information, please contact them directly.

Previous advisories and external security bulletins can be retrieved from:

        https://www.auscert.org.au/bulletins/

===========================================================================
Australian Computer Emergency Response Team
The University of Queensland
Brisbane
Qld 4072

Internet Email: auscert@auscert.org.au
Facsimile:      (07) 3365 7031
Telephone:      (07) 3365 4417 (International: +61 7 3365 4417)
                AusCERT personnel answer during Queensland business hours
                which are GMT+10:00 (AEST).
                On call after hours for member emergencies only.
===========================================================================
-----BEGIN PGP SIGNATURE-----
Comment: http://www.auscert.org.au/render.html?it=1967

iQIVAwUBYApiv+NLKJtyKPYoAQhO+A//e0dHUCY7SUlPtqTYdk6FATrJEik2bIjl
pH5pfKyQd+R7vF/y/e4wwYToNtse+49bOsO6x1t+Zmx3e5DhveVDyuNVN8r/GJeO
lSXa1AJGJPQAAefVArP5nllp3LkBJFp/vDaqL9unQQHxygukJJcF/LftuGo39APP
Eq7UJNbKsexNw4g8QOtCyQw+uSZA6bazRAUfDdhB85z6CPd5uhZcRynDWFUNe2j8
4ouavOkdWYHz76aft6SEnFZ4oqEfzUZBTpYPHCoWGsviwJ12MGRghv82mj9oUxCa
mPzvVIo0YAjqHP91R16w+zZKO9xzHT1KKPbnvc9CHKO/jq0+R26xE+Nc6rB+LFNg
F6OV+AzRyTylp3oPctyVzXjnF77xG0s5pDiWw4UEnAXwkKUYJ6IMnL/4pkqv3V6L
WCL4JY16XKvhTWCdSvnAPIeO5u5Z8iSQz4MBy0mG9BPnm5xMcBIb5U7M8psKJswm
uAahtn51L+Y6BTHy9PF53UYLKd9Y1N300wCG0XMP4LqJN1Uew973xeRNrjlTIVbM
1oOUwjiIWibM86q5D22xuT8uWHl6Q2rf3l5B/zl4U/VL4JXrZiyzs9ZXWIK8RZLi
+XXN5B/USEtltc0M5h3ENWS8biXzTQushTnCpSnVR4ogYvaXGVJdAVvrJwTyTlee
croxzzOtpPQ=
=fV24
-----END PGP SIGNATURE-----

Read More

The post ESB-2020.4547.2 – UPDATE [Appliance] BIG-IP and BIG-IQ products: Multiple vulnerabilities appeared first on Malware Devil.

https://malwaredevil.com/2021/01/22/esb-2020-4547-2-update-appliance-big-ip-and-big-iq-products-multiple-vulnerabilities/?utm_source=rss&utm_medium=rss&utm_campaign=esb-2020-4547-2-update-appliance-big-ip-and-big-iq-products-multiple-vulnerabilities

ESB-2021.0266 – [SUSE] samba: Multiple vulnerabilities

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

===========================================================================
             AUSCERT External Security Bulletin Redistribution

                               ESB-2021.0266
                         Security update for samba
                              22 January 2021

===========================================================================

        AusCERT Security Bulletin Summary
        ---------------------------------

Product:           samba
Publisher:         SUSE
Operating System:  SUSE
Impact/Access:     Increased Privileges     -- Existing Account
                   Denial of Service        -- Existing Account
                   Access Confidential Data -- Existing Account
Resolution:        Patch/Upgrade
CVE Names:         CVE-2020-14383 CVE-2020-14323 CVE-2020-14318

Reference:         ESB-2020.4436
                   ESB-2020.4143
                   ESB-2020.3755

Original Bulletin: 
   https://www.suse.com/support/update/announcement/2021/suse-su-20210185-1

- --------------------------BEGIN INCLUDED TEXT--------------------

SUSE Security Update: Security update for samba

______________________________________________________________________________

Announcement ID:   SUSE-SU-2021:0185-1
Rating:            moderate
References:        #1173902 #1173994 #1177355 #1177613 #1178469
Cross-References:  CVE-2020-14318 CVE-2020-14323 CVE-2020-14383
Affected Products:
                   SUSE Enterprise Storage 7
______________________________________________________________________________

An update that solves three vulnerabilities and has two fixes is now available.

Description:

This update for samba fixes the following issues:

  o Update to 4.13.3 + libcli: smb2: Never print length if
    smb2_signing_key_valid() fails for crypto blob; (bso#14210); + s3: modules:
    gluster. Fix the error I made in preventing talloc leaks from a function;
    (bso#14486); + s3: smbd: Don't overwrite contents of fsp->aio_requests[0]
    with NULL via TALLOC_FREE(); (bso#14515); + s3: spoolss: Make parameters in
    call to user_ok_token() match all other uses; (bso#14568); + s3: smbd:
    Quiet log messages from usershares for an unknown share; (bso#14590); +
    samba process does not honor max log size; (bso#14248); + vfs_zfsacl: Add
    missing inherited flag on hidden "magic" everyone@ ACE; (bso#14587); +
    s3-libads: Pass timeout to open_socket_out in ms; (bso#13124); +
    s3-vfs_glusterfs: Always disable write-behind translator; (bso#14486); +
    smbclient: Fix recursive mget; (bso#14517); + clitar: Use do_list()'s
    recursion in clitar.c; (bso#14581); + manpages/vfs_glusterfs: Mention
    silent skipping of write-behind translator; (bso#14486); +
    vfs_shadow_copy2: Preserve all open flags assuming ROFS; (bso#14573); +
    interface: Fix if_index is not parsed correctly; (bso#14514);


  o Update to 4.13.2 + s3: modules: vfs_glusterfs: Fix leak of char **lines
    onto mem_ctx on return; (bso#14486); + RN: vfs_zfsacl: Only grant
    DELETE_CHILD if ACL tag is special; (bso#14471); + smb.conf.5: Add
    clarification how configuration changes reflected by Samba; (bso#14538); +
    daemons: Report status to systemd even when running in foreground; (bso#
    14552); + DNS Resolver: Support both dnspython before and after 2.0.0; (bso
    #14553); + s3-vfs_glusterfs: Refuse connection when write-behind xlator is
    present; (bso#14486); + provision: Add support for BIND 9.16.x; (bso#
    14487); + ctdb-common: Avoid aliasing errors during code optimization; (bso
    #14537); + libndr: Avoid assigning duplicate versions to symbols; (bso#
    14541); + docs: Fix default value of spoolss:architecture; (bso#14522); +
    winbind: Fix a memleak; (bso#14388); + s4:dsdb:acl_read: Implement "List
    Object" mode feature; (bso#14531); + docs-xml/manpages: Add warning about
    write-behind translator for vfs_glusterfs; (bso#14486); + nsswitch/
    nsstest.c: Avoid nss function conflicts with glibc nss.h. +
    vfs_shadow_copy2: Avoid closing snapsdir twice; (bso#14530); + third_party:
    Update resolv_wrapper to version 1.1.7; (bso#14547); + examples:auth: Do
    not install example plugin; (bso#14550); + ctdb-recoverd: Drop unnecessary
    and broken code; (bso#14513); + RN: vfs_zfsacl: Only grant DELETE_CHILD if
    ACL tag is special; (bso#14471);


  o Adjust smbcacls '--propagate-inheritance' feature to align with upstream;
    (bsc#1178469).


  o Update to samba 4.13.1 + CVE-2020-14383: An authenticated user can crash
    the DCE/RPC DNS with easily crafted records; (bsc#1177613); (bso#14472); +
    CVE-2020-14323: Unprivileged user can crash winbind; (bsc#1173994); (bso#
    14436); + CVE-2020-14318: Missing handle permissions check in SMB1/2/3
    ChangeNotify; (bsc#1173902); (bso#14434);
  o Adjust systemd tmpfiles.d configuration, use /run/samba instead of /var/run
    /samba; (bsc#1177355);

Patch Instructions:

To install this SUSE Security Update use the SUSE recommended installation
methods like YaST online_update or "zypper patch".
Alternatively you can run the command listed for your product:

  o SUSE Enterprise Storage 7:
    zypper in -t patch SUSE-Storage-7-2021-185=1

Package List:

  o SUSE Enterprise Storage 7 (aarch64 x86_64):
       ctdb-4.13.3+git.181.fc4672a5b81-3.3.1
       ctdb-debuginfo-4.13.3+git.181.fc4672a5b81-3.3.1
       libdcerpc-binding0-4.13.3+git.181.fc4672a5b81-3.3.1
       libdcerpc-binding0-debuginfo-4.13.3+git.181.fc4672a5b81-3.3.1
       libdcerpc0-4.13.3+git.181.fc4672a5b81-3.3.1
       libdcerpc0-debuginfo-4.13.3+git.181.fc4672a5b81-3.3.1
       libndr-krb5pac0-4.13.3+git.181.fc4672a5b81-3.3.1
       libndr-krb5pac0-debuginfo-4.13.3+git.181.fc4672a5b81-3.3.1
       libndr-nbt0-4.13.3+git.181.fc4672a5b81-3.3.1
       libndr-nbt0-debuginfo-4.13.3+git.181.fc4672a5b81-3.3.1
       libndr-standard0-4.13.3+git.181.fc4672a5b81-3.3.1
       libndr-standard0-debuginfo-4.13.3+git.181.fc4672a5b81-3.3.1
       libndr1-4.13.3+git.181.fc4672a5b81-3.3.1
       libndr1-debuginfo-4.13.3+git.181.fc4672a5b81-3.3.1
       libnetapi0-4.13.3+git.181.fc4672a5b81-3.3.1
       libnetapi0-debuginfo-4.13.3+git.181.fc4672a5b81-3.3.1
       libsamba-credentials0-4.13.3+git.181.fc4672a5b81-3.3.1
       libsamba-credentials0-debuginfo-4.13.3+git.181.fc4672a5b81-3.3.1
       libsamba-errors0-4.13.3+git.181.fc4672a5b81-3.3.1
       libsamba-errors0-debuginfo-4.13.3+git.181.fc4672a5b81-3.3.1
       libsamba-hostconfig0-4.13.3+git.181.fc4672a5b81-3.3.1
       libsamba-hostconfig0-debuginfo-4.13.3+git.181.fc4672a5b81-3.3.1
       libsamba-passdb0-4.13.3+git.181.fc4672a5b81-3.3.1
       libsamba-passdb0-debuginfo-4.13.3+git.181.fc4672a5b81-3.3.1
       libsamba-util0-4.13.3+git.181.fc4672a5b81-3.3.1
       libsamba-util0-debuginfo-4.13.3+git.181.fc4672a5b81-3.3.1
       libsamdb0-4.13.3+git.181.fc4672a5b81-3.3.1
       libsamdb0-debuginfo-4.13.3+git.181.fc4672a5b81-3.3.1
       libsmbclient0-4.13.3+git.181.fc4672a5b81-3.3.1
       libsmbclient0-debuginfo-4.13.3+git.181.fc4672a5b81-3.3.1
       libsmbconf0-4.13.3+git.181.fc4672a5b81-3.3.1
       libsmbconf0-debuginfo-4.13.3+git.181.fc4672a5b81-3.3.1
       libsmbldap2-4.13.3+git.181.fc4672a5b81-3.3.1
       libsmbldap2-debuginfo-4.13.3+git.181.fc4672a5b81-3.3.1
       libtevent-util0-4.13.3+git.181.fc4672a5b81-3.3.1
       libtevent-util0-debuginfo-4.13.3+git.181.fc4672a5b81-3.3.1
       libwbclient0-4.13.3+git.181.fc4672a5b81-3.3.1
       libwbclient0-debuginfo-4.13.3+git.181.fc4672a5b81-3.3.1
       samba-4.13.3+git.181.fc4672a5b81-3.3.1
       samba-ceph-4.13.3+git.181.fc4672a5b81-3.3.1
       samba-ceph-debuginfo-4.13.3+git.181.fc4672a5b81-3.3.1
       samba-client-4.13.3+git.181.fc4672a5b81-3.3.1
       samba-client-debuginfo-4.13.3+git.181.fc4672a5b81-3.3.1
       samba-debuginfo-4.13.3+git.181.fc4672a5b81-3.3.1
       samba-debugsource-4.13.3+git.181.fc4672a5b81-3.3.1
       samba-libs-4.13.3+git.181.fc4672a5b81-3.3.1
       samba-libs-debuginfo-4.13.3+git.181.fc4672a5b81-3.3.1
       samba-libs-python3-4.13.3+git.181.fc4672a5b81-3.3.1
       samba-libs-python3-debuginfo-4.13.3+git.181.fc4672a5b81-3.3.1
       samba-winbind-4.13.3+git.181.fc4672a5b81-3.3.1
       samba-winbind-debuginfo-4.13.3+git.181.fc4672a5b81-3.3.1


References:

  o https://www.suse.com/security/cve/CVE-2020-14318.html
  o https://www.suse.com/security/cve/CVE-2020-14323.html
  o https://www.suse.com/security/cve/CVE-2020-14383.html
  o https://bugzilla.suse.com/1173902
  o https://bugzilla.suse.com/1173994
  o https://bugzilla.suse.com/1177355
  o https://bugzilla.suse.com/1177613
  o https://bugzilla.suse.com/1178469

- --------------------------END INCLUDED TEXT--------------------

You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.

NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members.  As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.

NOTE: This is only the original release of the security bulletin.  It may
not be updated when updates to the original are made.  If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.

Contact information for the authors of the original document is included
in the Security Bulletin above.  If you have any questions or need further
information, please contact them directly.

Previous advisories and external security bulletins can be retrieved from:

        https://www.auscert.org.au/bulletins/

===========================================================================
Australian Computer Emergency Response Team
The University of Queensland
Brisbane
Qld 4072

Internet Email: auscert@auscert.org.au
Facsimile:      (07) 3365 7031
Telephone:      (07) 3365 4417 (International: +61 7 3365 4417)
                AusCERT personnel answer during Queensland business hours
                which are GMT+10:00 (AEST).
                On call after hours for member emergencies only.
===========================================================================
-----BEGIN PGP SIGNATURE-----
Comment: http://www.auscert.org.au/render.html?it=1967

iQIVAwUBYApb9uNLKJtyKPYoAQjb/Q//cDlXYWjhH9EpxbO7+Au91orwWdOZgzGW
2CVEFXxk2dSG+z2lMtDl/tj2+Ni9hir8Fr6mkoOdJtnnHswrc1F0KcIf9mw5LExH
hLuUV5mE4fOZwIM9RMlx05mZDLgLQceEXt18k1mi6aP1mLdR8Q7Ii8Dl0gdNoiwT
IxXWfoGFFZipQ4lPmnk5k8YFs2Q4qNDGuY+rtwOiTMC3y2oMWhedHARwFagxg69b
iBirMXfVOQB75gzHpx+UaHk7QT5pNBHVQg4+viOC6Wzt54XCoigECGUhWSO7R2Bt
OShUoFQd9cjYV7KslJYa9GgD9Y73//4HC8l86Wz8Wy8q0ai0T4u560m8vxCYj1N9
bKD5NlcgcWL6zEyDuVW1LtcRcE3XkaPRyRpDVoPzQyyq5GWe3GN915GxhRyMy9Sk
o4kYQsSesxUgHbC8/0xTjP/4uvVE4nvkltttarGHB3oHRYK3P1NgY2kBUscZyR8f
tUldz4Go+2kXetp7EikVJiAkPfLla88u3+29imuScR3K6OuIqfjyqridAqvJaBzi
vtrtq4VK34zmWxErO/77KnWvE7kwNvSVR1+A6iKhFiQSdQK0RisGZ2QzIUst7goD
DcZEva3ABLMZ6LaXkGRn7XjfmISa9yW5aczTfYex1UVyhMjRWrbwqP45v0XvHiMu
O2qLgxgmNow=
=DowE
-----END PGP SIGNATURE-----

Read More

The post ESB-2021.0266 – [SUSE] samba: Multiple vulnerabilities appeared first on Malware Devil.

https://malwaredevil.com/2021/01/22/esb-2021-0266-suse-samba-multiple-vulnerabilities/?utm_source=rss&utm_medium=rss&utm_campaign=esb-2021-0266-suse-samba-multiple-vulnerabilities

ESB-2021.0265 – [SUSE] yast2-multipath: Overwrite arbitrary files – Existing account

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

===========================================================================
             AUSCERT External Security Bulletin Redistribution

                               ESB-2021.0265
                    Security update for yast2-multipath
                              22 January 2021

===========================================================================

        AusCERT Security Bulletin Summary
        ---------------------------------

Product:           yast2-multipath
Publisher:         SUSE
Operating System:  SUSE
Impact/Access:     Overwrite Arbitrary Files -- Existing Account
Resolution:        Patch/Upgrade
CVE Names:         CVE-2018-17955  

Reference:         ESB-2020.3912

Original Bulletin: 
   https://www.suse.com/support/update/announcement/2021/suse-su-20210182-1

- --------------------------BEGIN INCLUDED TEXT--------------------

SUSE Security Update: Security update for yast2-multipath

______________________________________________________________________________

Announcement ID:   SUSE-SU-2021:0182-1
Rating:            moderate
References:        #1026027 #1117592
Cross-References:  CVE-2018-17955
Affected Products:
                   SUSE Linux Enterprise High Availability 12-SP2
______________________________________________________________________________

An update that solves one vulnerability and has one errata is now available.

Description:

This update for yast2-multipath to version 3.1.9 fixes the following issues:
Security issue fixed:

  o CVE-2018-17955: Use random file name instead of static names (bsc#1117592).


Non-security issue fixed:

  o Removed calls to /sbin/insserv (bsc#1026027).

Patch Instructions:

To install this SUSE Security Update use the SUSE recommended installation
methods like YaST online_update or "zypper patch".
Alternatively you can run the command listed for your product:

  o SUSE Linux Enterprise High Availability 12-SP2:
    zypper in -t patch SUSE-SLE-HA-12-SP2-2021-182=1

Package List:

  o SUSE Linux Enterprise High Availability 12-SP2 (noarch):
       yast2-multipath-3.1.9-12.3.45


References:

  o https://www.suse.com/security/cve/CVE-2018-17955.html
  o https://bugzilla.suse.com/1026027
  o https://bugzilla.suse.com/1117592

- --------------------------END INCLUDED TEXT--------------------

You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.

NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members.  As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.

NOTE: This is only the original release of the security bulletin.  It may
not be updated when updates to the original are made.  If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.

Contact information for the authors of the original document is included
in the Security Bulletin above.  If you have any questions or need further
information, please contact them directly.

Previous advisories and external security bulletins can be retrieved from:

        https://www.auscert.org.au/bulletins/

===========================================================================
Australian Computer Emergency Response Team
The University of Queensland
Brisbane
Qld 4072

Internet Email: auscert@auscert.org.au
Facsimile:      (07) 3365 7031
Telephone:      (07) 3365 4417 (International: +61 7 3365 4417)
                AusCERT personnel answer during Queensland business hours
                which are GMT+10:00 (AEST).
                On call after hours for member emergencies only.
===========================================================================
-----BEGIN PGP SIGNATURE-----
Comment: http://www.auscert.org.au/render.html?it=1967

iQIVAwUBYApb2uNLKJtyKPYoAQhDaQ//bymcSyssZYCror1iAj0Ti4SIZNPboN/B
QFTt2oizynd0f3JClzhZblxwoK11W7YV80P9qrPPmBul5nQa8q4E/ody0GsxaAER
x8N01scQ1qzwIscEvDAquMuPPkek9OC1lRWHafCe9uLzxqDAF8xKHfzIi6MEhytc
+VjeoY/c8As+tgu5A6SWLy8oJxzAPD6A6nvB2q1LayOVTvaRCDEZbeQQiNiWk7Rk
bQ11sxuuWNZAv0jbUSe4okpImoz2+Hh1VU5tCrlEAFwR08x1uLP40eQgS6+gBF9T
oAk4GgilgcN33D6RNPGfBoHRy3bzksDoQsBhIbUZRY6LlYj1Du+jvQ0qhnVtHojx
/7GZBeo74uG+nDHZtfLNTNNQBKIorcjEUXuYwRIVgiHwQrIvKOwDRtuniX22qWWa
Job3aZ5rrLGSaEnQbTCh6z8oTTssE5zD1Rm4M/2BQCg3OU5ATQYVwEMSGbmVDpll
uInXycNxlxojLteNtpXxjN18KLy1vOf5xqgSPHQUfNcRGtDyN06Fyr9eIWzqkM4x
L0/y75mSpkjKNaVGgGVO2ufThFM332iPcOo3CHXBp7pqrrelPQfaMJVsRYxNcVd8
Wu7Y5yZDjhfeWM8SNGFrA/P2ZXsvmmNzIO/w8xhkzK7nkZhkG2X8DRBX2uqC1iTT
7vbrRqlMWdc=
=1f7W
-----END PGP SIGNATURE-----

Read More

The post ESB-2021.0265 – [SUSE] yast2-multipath: Overwrite arbitrary files – Existing account appeared first on Malware Devil.

https://malwaredevil.com/2021/01/22/esb-2021-0265-suse-yast2-multipath-overwrite-arbitrary-files-existing-account/?utm_source=rss&utm_medium=rss&utm_campaign=esb-2021-0265-suse-yast2-multipath-overwrite-arbitrary-files-existing-account

Network Security News Summary for Friday January 22nd, 2021

A brief daily summary of what is important in cybersecurity. The podcast is published every weekday and designed to get you ready for the day with a brief, usually about 5 minutes long, summary of current network security-related events. The content is late breaking, educational and based on listener input as well as on input received by the SANS Internet Storm Center. You may submit questions and comments via our contact form at https://isc.sans.edu/contact.html .

The post Network Security News Summary for Friday January 22nd, 2021 appeared first on Malware Devil.

https://malwaredevil.com/2021/01/22/network-security-news-summary-for-friday-january-22nd-2021/?utm_source=rss&utm_medium=rss&utm_campaign=network-security-news-summary-for-friday-january-22nd-2021

Penetration Testing Services

The post Penetration Testing Services appeared first on Digital Defense, Inc..

The post Penetration Testing Services appeared first on Security Boulevard.

Read More

The post Penetration Testing Services appeared first on Malware Devil.

https://malwaredevil.com/2021/01/21/penetration-testing-services/?utm_source=rss&utm_medium=rss&utm_campaign=penetration-testing-services

DreamBus, FreakOut Botnets Pose New Threat to Linux Systems

Researchers from Zscaler and Check Point describe botnets as designed for DDoS attacks, cryptocurrency mining, and other malicious purposes.

The post DreamBus, FreakOut Botnets Pose New Threat to Linux Systems appeared first on Malware Devil.

https://malwaredevil.com/2021/01/21/dreambus-freakout-botnets-pose-new-threat-to-linux-systems/?utm_source=rss&utm_medium=rss&utm_campaign=dreambus-freakout-botnets-pose-new-threat-to-linux-systems

Breach Data Shows Attackers Switched Gears in 2020

Attackers focused more on ransomware, while the consolidation of data into large databases led to fewer reported breaches but more records leaked.

The post Breach Data Shows Attackers Switched Gears in 2020 appeared first on Malware Devil.

https://malwaredevil.com/2021/01/21/breach-data-shows-attackers-switched-gears-in-2020/?utm_source=rss&utm_medium=rss&utm_campaign=breach-data-shows-attackers-switched-gears-in-2020

Attackers Leave Stolen Credentials Searchable on Google

Operators behind a global phishing campaign inadvertently left thousands of stolen credentials accessible via Google Search.

The post Attackers Leave Stolen Credentials Searchable on Google appeared first on Malware Devil.

https://malwaredevil.com/2021/01/21/attackers-leave-stolen-credentials-searchable-on-google/?utm_source=rss&utm_medium=rss&utm_campaign=attackers-leave-stolen-credentials-searchable-on-google

BullPhish ID is Fully Revamped and Raring to Go

The NEW improved BullPhish ID is packed with updates & upgrades that make phishing resistance training a snap for everyone!

The post BullPhish ID is Fully Revamped and Raring to Go appeared first on Security Boulevard.

Read More

The post BullPhish ID is Fully Revamped and Raring to Go appeared first on Malware Devil.

https://malwaredevil.com/2021/01/21/bullphish-id-is-fully-revamped-and-raring-to-go/?utm_source=rss&utm_medium=rss&utm_campaign=bullphish-id-is-fully-revamped-and-raring-to-go

Analyze Attacker Behavior, Endpoint Detection Anomalies with LogRhythm and Carbon Black

As cyberthreats continue to grow, enterprises like yours are challenged more than ever to protect the business from damage. And threats aren’t going away. By 2021, Cybercrime Magazine predicts a ransomware attack will occur on businesses every 11 seconds, up from…

The post Analyze Attacker Behavior, Endpoint Detection Anomalies with LogRhythm and Carbon Black   appeared first on LogRhythm.

The post Analyze Attacker Behavior, Endpoint Detection Anomalies with LogRhythm and Carbon Black   appeared first on Security Boulevard.

Read More

The post Analyze Attacker Behavior, Endpoint Detection Anomalies with LogRhythm and Carbon Black   appeared first on Malware Devil.

https://malwaredevil.com/2021/01/21/analyze-attacker-behavior-endpoint-detection-anomalies-with-logrhythm-and-carbon-black/?utm_source=rss&utm_medium=rss&utm_campaign=analyze-attacker-behavior-endpoint-detection-anomalies-with-logrhythm-and-carbon-black

Windows Certificate Export: Detections Inspired by the SolarWinds Compromise

TL/DR Methods to detect when a certificate is exported from a Windows system are discussed in detail below using the audit log “Certificate Services Lifecycle Notifications” and collecting the log messages with “MS Windows Event Logging XML – Generic” log…

The post Windows Certificate Export: Detections Inspired by the SolarWinds Compromise appeared first on LogRhythm.

The post Windows Certificate Export: Detections Inspired by the SolarWinds Compromise appeared first on Security Boulevard.

Read More

The post Windows Certificate Export: Detections Inspired by the SolarWinds Compromise appeared first on Malware Devil.

https://malwaredevil.com/2021/01/21/windows-certificate-export-detections-inspired-by-the-solarwinds-compromise/?utm_source=rss&utm_medium=rss&utm_campaign=windows-certificate-export-detections-inspired-by-the-solarwinds-compromise

Einstein Healthcare Network Announces August Breach

Einstein is in violation of the the HHS 60-day breach notification rule, but unlikely to face penalty.
Read More

The post Einstein Healthcare Network Announces August Breach appeared first on Malware Devil.

https://malwaredevil.com/2021/01/21/einstein-healthcare-network-announces-august-breach-2/?utm_source=rss&utm_medium=rss&utm_campaign=einstein-healthcare-network-announces-august-breach-2