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?

  1. 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.

  2. 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.

  • 1
    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 May 13 at 6:04

I opened a link you provided to grab the CVE number, then looked using a search engine for details


> 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 May 13 at 1:56

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 May 13 at 1:58

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
  • Hope this help me secure my blog :). Cause my blog suddenly had a corrupted plugin when I upgraded it which was fine before. – Abdul May 14 at 0:58
  • @Abdul No idea? You asked about the vulnerability in apt, not about your blog. – Michael Hampton May 14 at 0:59
  • Pardon me, I am new in ubuntu and have not much knowledge about it. I was thinking that If the vulnerability allowed people to install their binary, so it can damage the thing inside the server include my blog. Maybe I am paranoid. – Abdul May 14 at 1:08
  • @Abdul There is no way to prove that your machine wasn't already compromised. If you have reason to suspect a compromise, reinstall the OS. – Michael Hampton May 14 at 1:13

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.