Is this apt vulnerability (CVE-2019-3462) a security concern for Ubuntu users?Install GNOME extensions through website: security vulnerability?Does ubuntu allow users to run ESET Smart Security?Is this a security risk/concern?Priority field in CVE pages on http://people.ubuntu.com/~ubuntu-security/cve/CVE-XXXXis the current Adobe Flash 'ransomware vulnerability' affecting Ubuntu users?Add a repository for security testingURL for Ubuntu 16.04 security updatesIs there a RESTful API for the Ubuntu CVE Tracker?Ubuntu AMi for AWS with patch for Dirty cow VulnerabilityHow is the severity/priority of a vulnerability in the Ubuntu CVE tracker determined?
Are there any established rules for splitting books into parts, chapters, sections etc?
Why was Endgame Thanos so different than Infinity War Thanos?
Smallest Guaranteed hash collision cycle length
Developers demotivated due to working on same project for more than 2 years
Find hamming distance between two Strings of equal length in Java
Labeling matrices/rectangles and drawing Sigma inside rectangle
Can't find the release for this wiring harness connector
Why do the lights go out when someone enters the dining room on this ship?
Would an 8% reduction in drag outweigh the weight addition from this custom CFD-tested winglet?
As programers say: Strive to be lazy
Automatically anti-predictably assemble an alliterative aria
Can I say that master can only initiate communication in SPI vs. in I2C slave can also initiate the communication?
High Memory Utilization in Juniper ACX2100
Is Germany still exporting arms to countries involved in Yemen?
Will a coyote attack my dog on a leash while I'm on a hiking trail?
Extracting sublists that contain similar elements
How can a layman easily get the consensus view of what academia *thinks* about a subject?
Magento 2: How to get type columns of table in sql?
return tuple of uncopyable objects
Could there be a material that inverts the colours seen through it?
Wireless headphones interfere with Wi-Fi signal on laptop
51% attack - apparently very easy? refering to CZ's "rollback btc chain" - How to make sure such corruptible scenario can never happen so easily?
Is there ever any indication in the MCU as to how Spider-Man got his powers?
Area under the curve - Integrals (Antiderivatives)
Is this apt vulnerability (CVE-2019-3462) a security concern for Ubuntu users?
Install GNOME extensions through website: security vulnerability?Does ubuntu allow users to run ESET Smart Security?Is this a security risk/concern?Priority field in CVE pages on http://people.ubuntu.com/~ubuntu-security/cve/CVE-XXXXis the current Adobe Flash 'ransomware vulnerability' affecting Ubuntu users?Add a repository for security testingURL for Ubuntu 16.04 security updatesIs there a RESTful API for the Ubuntu CVE Tracker?Ubuntu AMi for AWS with patch for Dirty cow VulnerabilityHow is the severity/priority of a vulnerability in the Ubuntu CVE tracker determined?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I am new to Ubuntu server. I found this post about a vulnerability in Debian's APT. Do you think this issue has been resolved?
A vulnerability in Debian’s apt allows for easy lateral movement in data centers
On January 22nd, Max Justicz published a write up detailing a vulnerability in the apt client. Using Man in the Middle techniques, an attacker can intercept the apt communication while it downloads a software package, replace the requested package content with their own binary, and execute it with root privileges.
Remote Code Execution in apt/apt-get - Max Justicz
I found a vulnerability in apt that allows a network man-in-the-middle (or a malicious package mirror) to execute arbitrary code as root on a machine installing any package. The bug has been fixed in the latest versions of apt. If you’re worried about being exploited during the update process, you can protect yourself by disabling HTTP redirects while you update.
apt security
add a comment |
I am new to Ubuntu server. I found this post about a vulnerability in Debian's APT. Do you think this issue has been resolved?
A vulnerability in Debian’s apt allows for easy lateral movement in data centers
On January 22nd, Max Justicz published a write up detailing a vulnerability in the apt client. Using Man in the Middle techniques, an attacker can intercept the apt communication while it downloads a software package, replace the requested package content with their own binary, and execute it with root privileges.
Remote Code Execution in apt/apt-get - Max Justicz
I found a vulnerability in apt that allows a network man-in-the-middle (or a malicious package mirror) to execute arbitrary code as root on a machine installing any package. The bug has been fixed in the latest versions of apt. If you’re worried about being exploited during the update process, you can protect yourself by disabling HTTP redirects while you update.
apt security
It's good to summarise or include a relevant bit from the linked page into the question (or answer) in case the page disappears and to make what you're saying self-evident
– thomasrutter
28 mins ago
add a comment |
I am new to Ubuntu server. I found this post about a vulnerability in Debian's APT. Do you think this issue has been resolved?
A vulnerability in Debian’s apt allows for easy lateral movement in data centers
On January 22nd, Max Justicz published a write up detailing a vulnerability in the apt client. Using Man in the Middle techniques, an attacker can intercept the apt communication while it downloads a software package, replace the requested package content with their own binary, and execute it with root privileges.
Remote Code Execution in apt/apt-get - Max Justicz
I found a vulnerability in apt that allows a network man-in-the-middle (or a malicious package mirror) to execute arbitrary code as root on a machine installing any package. The bug has been fixed in the latest versions of apt. If you’re worried about being exploited during the update process, you can protect yourself by disabling HTTP redirects while you update.
apt security
I am new to Ubuntu server. I found this post about a vulnerability in Debian's APT. Do you think this issue has been resolved?
A vulnerability in Debian’s apt allows for easy lateral movement in data centers
On January 22nd, Max Justicz published a write up detailing a vulnerability in the apt client. Using Man in the Middle techniques, an attacker can intercept the apt communication while it downloads a software package, replace the requested package content with their own binary, and execute it with root privileges.
Remote Code Execution in apt/apt-get - Max Justicz
I found a vulnerability in apt that allows a network man-in-the-middle (or a malicious package mirror) to execute arbitrary code as root on a machine installing any package. The bug has been fixed in the latest versions of apt. If you’re worried about being exploited during the update process, you can protect yourself by disabling HTTP redirects while you update.
apt security
apt security
edited 9 mins ago
fkraiem
9,26332031
9,26332031
asked 6 hours ago
AbdulAbdul
305
305
It's good to summarise or include a relevant bit from the linked page into the question (or answer) in case the page disappears and to make what you're saying self-evident
– thomasrutter
28 mins ago
add a comment |
It's good to summarise or include a relevant bit from the linked page into the question (or answer) in case the page disappears and to make what you're saying self-evident
– thomasrutter
28 mins ago
It's good to summarise or include a relevant bit from the linked page into the question (or answer) in case the page disappears and to make what you're saying self-evident
– thomasrutter
28 mins ago
It's good to summarise or include a relevant bit from the linked page into the question (or answer) in case the page disappears and to make what you're saying self-evident
– thomasrutter
28 mins ago
add a comment |
3 Answers
3
active
oldest
votes
I opened a link you provided to grab the CVE number, then looked using a search engine for details
https://people.canonical.com/~ubuntu-security/cve/2019/CVE-2019-3462.html
> Ubuntu 12.04 ESM (Precise Pangolin): released
> (0.8.16~exp12ubuntu10.28)
> Ubuntu 14.04 LTS (Trusty Tahr): released
> (1.0.1ubuntu2.19) Ubuntu 16.04 LTS (Xenial Xerus): released
> (1.2.29ubuntu0.1) Ubuntu 18.04 LTS (Bionic Beaver): released
> (1.6.6ubuntu0.1) Ubuntu 18.10 (Cosmic Cuttlefish): released
> (1.7.0ubuntu0.1) Ubuntu 19.04 (Disco Dingo): released (1.8.0~alpha3.1)
As long as you have the packages listed as containing the fix you'll be fine. For more details, check Ubuntu security notes.
Thanks the info. Hope this help me to use Ubuntu again.
– Abdul
4 hours ago
add a comment |
Yes, it's definitely fixed.
The best way to track security issues is using a CVE number. That's what CVE numbers are for. In this case, you seem to be worried about CVE-2019-3462
CVEs may have more than one related bug report. You can find all the bugs for this particular CVE at https://bugs.launchpad.net/bugs/cve/2019-3462. The bug tracker will tell you which bugs are fixed in which releases of Ubuntu, and when the fixes were uploaded.
After fixing this particular CVE, the Ubuntu Security Team talked about this issue and the fix in their podcast of 29 January 2019. It's brief, and worth a listen.
Glad to know that. Thanks
– Abdul
4 hours ago
add a comment |
When speaking of security vulnerabilities, the so-called CVE number is used across the entire industry to refer to a specific vulnerability. Everyone who responds to the vulnerability, regardless of Linux distribution, will use the same CVE number to refer to it.
In the articles you referenced, the CVE number was shown: CVE-2019-3462
Once you have the CVE number for any security issue, you can look it up in the Ubuntu CVE Tracker to find its current status in Ubuntu, including:
- A description of the vulnerability
- Links to Ubuntu Security Notices for the vulnerability, if available
- The status of the vulnerability in each supported Ubuntu distribution
- Package version numbers of fixed packages, when they become available
- External links to information about the vulnerability
When the status for your distribution shows as "released" then a package with the fix is ready to download, and should be available after the next time you run sudo apt update
.
To check the version of a package that you have installed, you can use dpkg -s
. For example:
error@vmtest-ubuntu1804:~$ dpkg -s apt | grep ^Version
Version: 1.6.10
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1142734%2fis-this-apt-vulnerability-cve-2019-3462-a-security-concern-for-ubuntu-users%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
I opened a link you provided to grab the CVE number, then looked using a search engine for details
https://people.canonical.com/~ubuntu-security/cve/2019/CVE-2019-3462.html
> Ubuntu 12.04 ESM (Precise Pangolin): released
> (0.8.16~exp12ubuntu10.28)
> Ubuntu 14.04 LTS (Trusty Tahr): released
> (1.0.1ubuntu2.19) Ubuntu 16.04 LTS (Xenial Xerus): released
> (1.2.29ubuntu0.1) Ubuntu 18.04 LTS (Bionic Beaver): released
> (1.6.6ubuntu0.1) Ubuntu 18.10 (Cosmic Cuttlefish): released
> (1.7.0ubuntu0.1) Ubuntu 19.04 (Disco Dingo): released (1.8.0~alpha3.1)
As long as you have the packages listed as containing the fix you'll be fine. For more details, check Ubuntu security notes.
Thanks the info. Hope this help me to use Ubuntu again.
– Abdul
4 hours ago
add a comment |
I opened a link you provided to grab the CVE number, then looked using a search engine for details
https://people.canonical.com/~ubuntu-security/cve/2019/CVE-2019-3462.html
> Ubuntu 12.04 ESM (Precise Pangolin): released
> (0.8.16~exp12ubuntu10.28)
> Ubuntu 14.04 LTS (Trusty Tahr): released
> (1.0.1ubuntu2.19) Ubuntu 16.04 LTS (Xenial Xerus): released
> (1.2.29ubuntu0.1) Ubuntu 18.04 LTS (Bionic Beaver): released
> (1.6.6ubuntu0.1) Ubuntu 18.10 (Cosmic Cuttlefish): released
> (1.7.0ubuntu0.1) Ubuntu 19.04 (Disco Dingo): released (1.8.0~alpha3.1)
As long as you have the packages listed as containing the fix you'll be fine. For more details, check Ubuntu security notes.
Thanks the info. Hope this help me to use Ubuntu again.
– Abdul
4 hours ago
add a comment |
I opened a link you provided to grab the CVE number, then looked using a search engine for details
https://people.canonical.com/~ubuntu-security/cve/2019/CVE-2019-3462.html
> Ubuntu 12.04 ESM (Precise Pangolin): released
> (0.8.16~exp12ubuntu10.28)
> Ubuntu 14.04 LTS (Trusty Tahr): released
> (1.0.1ubuntu2.19) Ubuntu 16.04 LTS (Xenial Xerus): released
> (1.2.29ubuntu0.1) Ubuntu 18.04 LTS (Bionic Beaver): released
> (1.6.6ubuntu0.1) Ubuntu 18.10 (Cosmic Cuttlefish): released
> (1.7.0ubuntu0.1) Ubuntu 19.04 (Disco Dingo): released (1.8.0~alpha3.1)
As long as you have the packages listed as containing the fix you'll be fine. For more details, check Ubuntu security notes.
I opened a link you provided to grab the CVE number, then looked using a search engine for details
https://people.canonical.com/~ubuntu-security/cve/2019/CVE-2019-3462.html
> Ubuntu 12.04 ESM (Precise Pangolin): released
> (0.8.16~exp12ubuntu10.28)
> Ubuntu 14.04 LTS (Trusty Tahr): released
> (1.0.1ubuntu2.19) Ubuntu 16.04 LTS (Xenial Xerus): released
> (1.2.29ubuntu0.1) Ubuntu 18.04 LTS (Bionic Beaver): released
> (1.6.6ubuntu0.1) Ubuntu 18.10 (Cosmic Cuttlefish): released
> (1.7.0ubuntu0.1) Ubuntu 19.04 (Disco Dingo): released (1.8.0~alpha3.1)
As long as you have the packages listed as containing the fix you'll be fine. For more details, check Ubuntu security notes.
edited 6 hours ago
answered 6 hours ago
guivercguiverc
5,46921723
5,46921723
Thanks the info. Hope this help me to use Ubuntu again.
– Abdul
4 hours ago
add a comment |
Thanks the info. Hope this help me to use Ubuntu again.
– Abdul
4 hours ago
Thanks the info. Hope this help me to use Ubuntu again.
– Abdul
4 hours ago
Thanks the info. Hope this help me to use Ubuntu again.
– Abdul
4 hours ago
add a comment |
Yes, it's definitely fixed.
The best way to track security issues is using a CVE number. That's what CVE numbers are for. In this case, you seem to be worried about CVE-2019-3462
CVEs may have more than one related bug report. You can find all the bugs for this particular CVE at https://bugs.launchpad.net/bugs/cve/2019-3462. The bug tracker will tell you which bugs are fixed in which releases of Ubuntu, and when the fixes were uploaded.
After fixing this particular CVE, the Ubuntu Security Team talked about this issue and the fix in their podcast of 29 January 2019. It's brief, and worth a listen.
Glad to know that. Thanks
– Abdul
4 hours ago
add a comment |
Yes, it's definitely fixed.
The best way to track security issues is using a CVE number. That's what CVE numbers are for. In this case, you seem to be worried about CVE-2019-3462
CVEs may have more than one related bug report. You can find all the bugs for this particular CVE at https://bugs.launchpad.net/bugs/cve/2019-3462. The bug tracker will tell you which bugs are fixed in which releases of Ubuntu, and when the fixes were uploaded.
After fixing this particular CVE, the Ubuntu Security Team talked about this issue and the fix in their podcast of 29 January 2019. It's brief, and worth a listen.
Glad to know that. Thanks
– Abdul
4 hours ago
add a comment |
Yes, it's definitely fixed.
The best way to track security issues is using a CVE number. That's what CVE numbers are for. In this case, you seem to be worried about CVE-2019-3462
CVEs may have more than one related bug report. You can find all the bugs for this particular CVE at https://bugs.launchpad.net/bugs/cve/2019-3462. The bug tracker will tell you which bugs are fixed in which releases of Ubuntu, and when the fixes were uploaded.
After fixing this particular CVE, the Ubuntu Security Team talked about this issue and the fix in their podcast of 29 January 2019. It's brief, and worth a listen.
Yes, it's definitely fixed.
The best way to track security issues is using a CVE number. That's what CVE numbers are for. In this case, you seem to be worried about CVE-2019-3462
CVEs may have more than one related bug report. You can find all the bugs for this particular CVE at https://bugs.launchpad.net/bugs/cve/2019-3462. The bug tracker will tell you which bugs are fixed in which releases of Ubuntu, and when the fixes were uploaded.
After fixing this particular CVE, the Ubuntu Security Team talked about this issue and the fix in their podcast of 29 January 2019. It's brief, and worth a listen.
answered 4 hours ago
user535733user535733
9,28633045
9,28633045
Glad to know that. Thanks
– Abdul
4 hours ago
add a comment |
Glad to know that. Thanks
– Abdul
4 hours ago
Glad to know that. Thanks
– Abdul
4 hours ago
Glad to know that. Thanks
– Abdul
4 hours ago
add a comment |
When speaking of security vulnerabilities, the so-called CVE number is used across the entire industry to refer to a specific vulnerability. Everyone who responds to the vulnerability, regardless of Linux distribution, will use the same CVE number to refer to it.
In the articles you referenced, the CVE number was shown: CVE-2019-3462
Once you have the CVE number for any security issue, you can look it up in the Ubuntu CVE Tracker to find its current status in Ubuntu, including:
- A description of the vulnerability
- Links to Ubuntu Security Notices for the vulnerability, if available
- The status of the vulnerability in each supported Ubuntu distribution
- Package version numbers of fixed packages, when they become available
- External links to information about the vulnerability
When the status for your distribution shows as "released" then a package with the fix is ready to download, and should be available after the next time you run sudo apt update
.
To check the version of a package that you have installed, you can use dpkg -s
. For example:
error@vmtest-ubuntu1804:~$ dpkg -s apt | grep ^Version
Version: 1.6.10
add a comment |
When speaking of security vulnerabilities, the so-called CVE number is used across the entire industry to refer to a specific vulnerability. Everyone who responds to the vulnerability, regardless of Linux distribution, will use the same CVE number to refer to it.
In the articles you referenced, the CVE number was shown: CVE-2019-3462
Once you have the CVE number for any security issue, you can look it up in the Ubuntu CVE Tracker to find its current status in Ubuntu, including:
- A description of the vulnerability
- Links to Ubuntu Security Notices for the vulnerability, if available
- The status of the vulnerability in each supported Ubuntu distribution
- Package version numbers of fixed packages, when they become available
- External links to information about the vulnerability
When the status for your distribution shows as "released" then a package with the fix is ready to download, and should be available after the next time you run sudo apt update
.
To check the version of a package that you have installed, you can use dpkg -s
. For example:
error@vmtest-ubuntu1804:~$ dpkg -s apt | grep ^Version
Version: 1.6.10
add a comment |
When speaking of security vulnerabilities, the so-called CVE number is used across the entire industry to refer to a specific vulnerability. Everyone who responds to the vulnerability, regardless of Linux distribution, will use the same CVE number to refer to it.
In the articles you referenced, the CVE number was shown: CVE-2019-3462
Once you have the CVE number for any security issue, you can look it up in the Ubuntu CVE Tracker to find its current status in Ubuntu, including:
- A description of the vulnerability
- Links to Ubuntu Security Notices for the vulnerability, if available
- The status of the vulnerability in each supported Ubuntu distribution
- Package version numbers of fixed packages, when they become available
- External links to information about the vulnerability
When the status for your distribution shows as "released" then a package with the fix is ready to download, and should be available after the next time you run sudo apt update
.
To check the version of a package that you have installed, you can use dpkg -s
. For example:
error@vmtest-ubuntu1804:~$ dpkg -s apt | grep ^Version
Version: 1.6.10
When speaking of security vulnerabilities, the so-called CVE number is used across the entire industry to refer to a specific vulnerability. Everyone who responds to the vulnerability, regardless of Linux distribution, will use the same CVE number to refer to it.
In the articles you referenced, the CVE number was shown: CVE-2019-3462
Once you have the CVE number for any security issue, you can look it up in the Ubuntu CVE Tracker to find its current status in Ubuntu, including:
- A description of the vulnerability
- Links to Ubuntu Security Notices for the vulnerability, if available
- The status of the vulnerability in each supported Ubuntu distribution
- Package version numbers of fixed packages, when they become available
- External links to information about the vulnerability
When the status for your distribution shows as "released" then a package with the fix is ready to download, and should be available after the next time you run sudo apt update
.
To check the version of a package that you have installed, you can use dpkg -s
. For example:
error@vmtest-ubuntu1804:~$ dpkg -s apt | grep ^Version
Version: 1.6.10
edited 32 mins ago
answered 40 mins ago
Michael HamptonMichael Hampton
1,050821
1,050821
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1142734%2fis-this-apt-vulnerability-cve-2019-3462-a-security-concern-for-ubuntu-users%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
It's good to summarise or include a relevant bit from the linked page into the question (or answer) in case the page disappears and to make what you're saying self-evident
– thomasrutter
28 mins ago