Overly broad permissions can turn one compromised account into a much larger security problem. Learn how to reduce unnecessary access, review privileges, and apply least privilege across modern Linux systems. Review Linux Privileges×

Alerts This Week
Warning Icon 1 542
Alerts This Week
Warning Icon 1 542

Stay Secure with the Latest Linux Advisories

Filter%20icon Refine advisories
X Clear Filters
X Clear Filters
View More

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Community Poll

Should Linux servers automatically install security updates?

No answer selected. Please try again.
Please select either existing option or enter your own, however not both.
Please select minimum {0} answer(s).
Please select maximum {0} answer(s).
/main-polls/157-should-linux-servers-automatically-install-security-updates?task=poll.vote&format=json
157
radio
0
[{"id":506,"title":"Yes \u2014 critical security patches should install automatically.","votes":0,"type":"x","order":1,"pct":0,"resources":[]},{"id":507,"title":"No \u2014 every update should be tested before deployment.","votes":0,"type":"x","order":2,"pct":0,"resources":[]},{"id":508,"title":"Only critical vulnerabilities should auto-install.","votes":0,"type":"x","order":3,"pct":0,"resources":[]},{"id":509,"title":"I patch when Reddit starts panicking.","votes":1,"type":"x","order":4,"pct":100,"resources":[]}] ["#ff5b00","#4ac0f2","#b80028","#eef66c","#60bb22","#b96a9a","#62c2cc"] ["rgba(255,91,0,0.7)","rgba(74,192,242,0.7)","rgba(184,0,40,0.7)","rgba(238,246,108,0.7)","rgba(96,187,34,0.7)","rgba(185,106,154,0.7)","rgba(98,194,204,0.7)"] 350
bottom 200
Loading...

Explore Latest Linux Security advisories

We found -8 articles for you...
100

openSUSE: SUSE-SA:2021:045 Critical: Adobe Reader Security Flaw

Acrobat Reader was updated to version 9.3.3 to fix lots of security Acrobat Reader was updated to version 9.3.3 to fix lots of security issues and bugs, several of whom could be used to execute code by issues and bugs, several of whom could be used to execute code by trick the target user to open specially crafted PDFs. Adobes advisory can be found here: [More...]. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ______________________________________________________________________________ SUSE Security Announcement Package: acroread Announcement ID: SUSE-SA:2010:029 Date: Thu, 08 Jul 2010 11:00:00 +0000 Affected Products: openSUSE 11.0 openSUSE 11.1 openSUSE 11.2 SUSE Linux Enterprise Desktop 10 SP3 SUSE Linux Enterprise Desktop 11 SUSE Linux Enterprise Desktop 11 SP1 Vulnerability Type: remote code execution CVSS v2 Base Score: 9.3 (AV:N/AC:M/Au:N/C:C/I:C/A:C) SUSE Default Package: yes Cross-References: CVE-2010-1240, CVE-2010-1285, CVE-2010-1295 CVE-2010-1297, CVE-2010-2168, CVE-2010-2201 CVE-2010-2202, CVE-2010-2203, CVE-2010-2204 CVE-2010-2205, CVE-2010-2206, CVE-2010-2207 CVE-2010-2208, CVE-2010-2209, CVE-2010-2210 CVE-2010-2211, CVE-2010-2212, APSB10-15 Content of This Advisory: 1) Security Vulnerability Resolved: Acrobat Reader security update Problem Description 2) Solution or Work-Around 3) Special Instructions and Notes 4) Package Location and Checksums 5) Pending Vulnerabilities, Solutions, and Work-Arounds: Summary Report. 6) AuthenticityVerification and Additional Information ______________________________________________________________________________ 1) Problem Description and Brief Discussion Acrobat Reader was updated to version 9.3.3 to fix lots of security issues and bugs, several of whom could be used to execute code by trick the target user to open specially crafted PDFs. Adobes advisory can be found here: etins/apsb10-15.html 2) Solution or Work-Around There is no known workaround, please install the update packages. 3) Special Instructions and Notes Please close and restart all running instances of Acrobat Reader after the update. 4) Package Location and Checksums The preferred method for installing security updates is to use the YaST Online Update (YOU) tool. YOU detects which updates are required and automatically performs the necessary steps to verify and install them. Alternatively, download the update packages for your distribution manually and verify their integrity by the methods listed in Section 6 of this announcement. Then install the packages using the command rpm -Fhv to apply the update, replacing with the filename of the downloaded RPM package. x86 Platform: openSUSE 11.2: http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/i586/acroread-9.3.3-2.1.1.i586.rpm openSUSE 11.1: http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.1/rpm/i586/acroread-9.3.3-2.1.1.i586.rpm openSUSE 11.0: http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.0/rpm/i586/acroread-9.3.3-2.1.i586.rpm Platform Independent: openSUSE 11.2: http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/noarch/acroread-cmaps-9.3.3-2.1.1.noarch.rpm http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/noarch/acroread-fonts-ja-9.3.3-2.1.1.noarch.rpm http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/noarch/acroread-fonts-ko-9.3.3-2.1.1.noarch.rpm http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/noarch/acroread-fonts-zh_CN-9.3.3-2.1.1.noarch.rpm http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.2/rpm/noarch/acroread-fonts-zh_TW-9.3.3-2.1.1.noarch.rpm openSUSE 11.1: http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.1/rpm/noarch/acroread-cmaps-9.3.3-2.1.1.noarch.rpm http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.1/rpm/noarch/acroread-fonts-ja-9.3.3-2.1.1.noarch.rpm http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.1/rpm/noarch/acroread-fonts-ko-9.3.3-2.1.1.noarch.rpm http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.1/rpm/noarch/acroread-fonts-zh_CN-9.3.3-2.1.1.noarch.rpm http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.1/rpm/noarch/acroread-fonts-zh_TW-9.3.3-2.1.1.noarch.rpm openSUSE 11.0: http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.0/rpm/noarch/acroread-cmaps-9.3.3-2.1.noarch.rpm http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.0/rpm/noarch/acroread-fonts-ja-9.3.3-2.1.noarch.rpm http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.0/rpm/noarch/acroread-fonts-ko-9.3.3-2.1.noarch.rpm http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.0/rpm/noarch/acroread-fonts-zh_CN-9.3.3-2.1.noarch.rpm http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.0/rpm/noarch/acroread-fonts-zh_TW-9.3.3-2.1.noarch.rpm Sources: openSUSE 11.2: openSUSE 11.1: openSUSE 11.0: http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.0/rpm/src/acroread-9.3.3-2.1.nosrc.rpm http://ftp5.gwdg.de/pub/opensuse/discontinued/update/11.0/rpm/src/acroread-cmaps-9.3.3-2.1.nosrc.rpm Our maintenance customers are notified individually. The packages are offered for installation from the maintenance web: SUSE Linux Enterprise Desktop 10 SP3 SUSE Linux Enterprise Desktop 11 SP1 SUSE Linux Enterprise Desktop 11 ______________________________________________________________________________ 5)Pending Vulnerabilities, Solutions, and Work-Arounds: See SUSE Security Summary Report. ______________________________________________________________________________ 6) Authenticity Verification and Additional Information - Announcement authenticity verification: SUSE security announcements are published via mailing lists and on Web sites. The authenticity and integrity of a SUSE security announcement is guaranteed by a cryptographic signature in each announcement. All SUSE security announcements are published with a valid signature. To verify the signature of the announcement, save it as text into a file and run the command gpg --verify replacing with the name of the file where you saved the announcement. The output for a valid signature looks like: gpg: Signature made using RSA key ID 3D25D3D9 gpg: Good signature from "SuSE Security Team " where is replaced by the date the document was signed. If the security team's key is not contained in your key ring, you can import it from the first installation CD. To import the key, use the command gpg --import gpg-pubkey-3d25d3d9-36e12d04.asc - Package authenticity verification: SUSE update packages are available on many mirror FTP servers all over the world. While this service is considered valuable and important to the free and open source software community, the authenticity and the integrity of a package needs to be verified to ensure that it has not been tampered with. The internal rpm package signatures provide an easy way to verify the authenticity of an RPM package. Use the command rpm -v --checksig to verify the signature of the package, replacing with the filename of the RPM package downloaded. The package is unmodified if it contains a valid signature from This email address is being protected from spambots. You need JavaScript enabled to view it. with the key ID 9C800ACA. This key is automatically imported into the RPM database (on RPMv4-based distributions) and the gpg keyring of 'root' during installation. You can also find it on the first installation CD and at the end of this announcement. - SUSE runs two security mailing lists to which any interested party may subscribe: This email address is being protected from spambots. You need JavaScript enabled to view it. - General Linux and SUSE security discussion. All SUSE security announcements are sent to this list. To subscribe, send an e-mail to . This email address is being protected from spambots. You need JavaScript enabled to view it. - SUSE's announce-only mailing list. Only SUSE's security announcements are sent to this list. To subscribe, send an e-mail to . ==================================================================== SUSE's security contact is or . The public key is listed below. ==================================================================== . Urgent patch released for Acrobat Reader addressing remote exploit vulnerabilities in openSUSE. Update immediately.. Acrobat Reader, security update, openSUSE, remote code exec. . Severity: Critical. LinuxSecurity.com Team

Calendar%202 Jul 08, 2010 Critical SuSE
News Add Esm H240

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Community Poll

Should Linux servers automatically install security updates?

No answer selected. Please try again.
Please select either existing option or enter your own, however not both.
Please select minimum {0} answer(s).
Please select maximum {0} answer(s).
/main-polls/157-should-linux-servers-automatically-install-security-updates?task=poll.vote&format=json
157
radio
0
[{"id":506,"title":"Yes \u2014 critical security patches should install automatically.","votes":0,"type":"x","order":1,"pct":0,"resources":[]},{"id":507,"title":"No \u2014 every update should be tested before deployment.","votes":0,"type":"x","order":2,"pct":0,"resources":[]},{"id":508,"title":"Only critical vulnerabilities should auto-install.","votes":0,"type":"x","order":3,"pct":0,"resources":[]},{"id":509,"title":"I patch when Reddit starts panicking.","votes":1,"type":"x","order":4,"pct":100,"resources":[]}] ["#ff5b00","#4ac0f2","#b80028","#eef66c","#60bb22","#b96a9a","#62c2cc"] ["rgba(255,91,0,0.7)","rgba(74,192,242,0.7)","rgba(184,0,40,0.7)","rgba(238,246,108,0.7)","rgba(96,187,34,0.7)","rgba(185,106,154,0.7)","rgba(98,194,204,0.7)"] 350
bottom 200