The CVE’s They are A-Changing!, (Wed, Apr 17th)

The downloadable format of CVE&#;x26;#;39;s from Miter will be changing in June 2024, so if you are using CVE downloads to populate your scanner, SIEM or to feed a SOC process, now would be a good time to look at that. If you are a vendor and use these downloads to populate your own feeds or product database, if you&#;x26;#;39;re not using the new format already you might be behind the eight ball!

Continue reading The CVE’s They are A-Changing!, (Wed, Apr 17th)

Posted in Uncategorized

Malicious PDF File Used As Delivery Mechanism, (Wed, Apr 17th)

Billions of PDF files are exchanged daily and many people trust them because they think the file is “read-only” and contains just “a bunch of data”. In the past, badly crafted PDF files could trigger nasty vulnerabilities in PDF viewers. All of them were affected at least once, especially Acrobat or FoxIt readers. A PDF file can also be pretty “dynamic” and embed JavaScript scripts, auto-open action to trigger the execution of a script (for example PowerShell on Windows, etc), or any other type of embedded data.

Continue reading Malicious PDF File Used As Delivery Mechanism, (Wed, Apr 17th)

Posted in Uncategorized

Rolling Back Packages on Ubuntu/Debian, (Tue, Apr 16th)

Package updates/upgrades by maintainers on the Linux platforms are always appreciated, as these updates are intended to offer new features/bug fixes. However, in rare circumstances, there is a need to downgrade the packages to a prior version due to unintended bugs or potential security issues, such as the recent xz-utils backdoor. Consistently backing up your data before significant updates is one good countermeasure against grief. However, what if one was not diligently practicing such measures and urgently needed to simply roll back to a prior version of the said package? I was recently put in this unenviable position when configuring one of my systems, and somehow, the latest version of Proton VPN (version 4.3.0) would not work and displayed the following output after I executed it:

Continue reading Rolling Back Packages on Ubuntu/Debian, (Tue, Apr 16th)

Posted in Uncategorized

Rolling Back Packages on Ubuntu/Debian, (Tue, Apr 16th)

Package updates/upgrades by maintainers on the Linux platforms are always appreciated, as these updates are intended to offer new features/bug fixes. However, in rare circumstances, there is a need to downgrade the packages to a prior version due to unintended bugs or potential security issues, such as the recent xz-utils backdoor. Consistently backing up your data before significant updates is one good countermeasure against grief. However, what if one was not diligently practicing such measures and urgently needed to simply roll back to a prior version of the said package? I was recently put in this unenviable position when configuring one of my systems, and somehow, the latest version of Proton VPN (version 4.3.0) would not work and displayed the following output after I executed it:

Continue reading Rolling Back Packages on Ubuntu/Debian, (Tue, Apr 16th)

Posted in Uncategorized

Rolling Back Packages on Ubuntu/Debian, (Tue, Apr 16th)

Package updates/upgrades by maintainers on the Linux platforms are always appreciated, as these updates are intended to offer new features/bug fixes. However, in rare circumstances, there is a need to downgrade the packages to a prior version due to unintended bugs or potential security issues, such as the recent xz-utils backdoor. Consistently backing up your data before significant updates is one good countermeasure against grief. However, what if one was not diligently practicing such measures and urgently needed to simply roll back to a prior version of the said package? I was recently put in this unenviable position when configuring one of my systems, and somehow, the latest version of Proton VPN (version 4.3.0) would not work and displayed the following output after I executed it:

Continue reading Rolling Back Packages on Ubuntu/Debian, (Tue, Apr 16th)

Posted in Uncategorized