Mageia vulnerabilities2 known to be exploited.

Vendor2 known exploited
The short answer

Mageia has 22 published vulnerabilities across 1 product in our catalogue. 2 of them are on the list of flaws known to be exploited, so criminals are using them now. The most affected product is Mageia, with 22. If you run Mageia software, patch the exploited flaws first.

See the exploited flaws

The most recent Mageia flaw added to the known-exploited list is CVE-2014-6271, on 28 January 2022. We keep watching the known-exploited list.

Products

Which Mageia products have the most vulnerabilities?

Mageia leads with 22 published vulnerabilities. Open a product to see its versions and which of its flaws criminals are already using.

  1. Mageia22
Published vulnerabilities
Known exploited

Which Mageia vulnerabilities are being exploited?

2 flaws are on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.

  1. 9.8
    CVE-2014-6271CriticalKnown exploited
    GNU Bourne-Again Shell (Bash) Arbitrary Code Execution Vulnerability

    GNU Bash through 4.3 processes trailing strings after function definitions in the values of environment variables, which allows remote attackers to execute code.

    Chance of use>99%Known exploited since28 Jan 2022
  2. 9.8
    CVE-2014-7169CriticalKnown exploited
    GNU Bourne-Again Shell (Bash) Arbitrary Code Execution Vulnerability

    GNU Bash through 4.3 processes trailing strings after function definitions in the values of environment variables, which allows remote attackers to execute code.

    Chance of use>99%Known exploited since28 Jan 2022
Exploit likelihood

Which Mageia flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. >99%
    CVE-2014-6271CriticalKnown exploited

    GNU Bash through 4.3 processes trailing strings after function definitions in the values of environment variables, which allows remote attackers to execute arbitrary code via a crafted environment, as demonstrated by...

    CVSS9.8Published24 Sep 2014
  2. >99%

    The SSL protocol 3.0, as used in OpenSSL through 1.0.1i and other products, uses nondeterministic CBC padding, which makes it easier for man-in-the-middle attackers to obtain cleartext data via a padding-oracle...

    CVSS3.4Published15 Oct 2014
  3. >99%
    CVE-2014-7169CriticalKnown exploited

    GNU Bash through 4.3 bash43-025 processes trailing strings after certain malformed function definitions in the values of environment variables, which allows remote attackers to write to files or possibly have unknown...

    CVSS9.8Published25 Sep 2014
  4. 12%

    Buffer overflow in the vararg functions in ldo.c in Lua 5.1 through 5.2.x before 5.2.3 allows context-dependent attackers to cause a denial of service (crash) via a small number of arguments to a function with a...

    CVSS5.0Published4 Sep 2014
  5. 9.7%

    The write_one_header function in mutt 1.5.23 does not properly handle newline characters at the beginning of a header, which allows remote attackers to cause a denial of service (crash) via a header with an empty...

    CVSS5.0Published2 Dec 2014
  6. 5.9%

    softmagic.c in file before 5.21 does not properly limit recursion, which allows remote attackers to cause a denial of service (CPU consumption or crash) via unspecified vectors.

    CVSS5.0Published17 Dec 2014
  7. 5.7%

    Integer underflow in the ksba_oid_to_str function in Libksba before 1.3.2, as used in GnuPG, allows remote attackers to cause a denial of service (crash) via a crafted OID in a (1) S/MIME message or (2) ECC based...

    CVSS7.5Published1 Dec 2014
  8. 4.8%

    jscript.c in Exuberant Ctags 5.8 allows remote attackers to cause a denial of service (infinite loop and CPU and disk consumption) via a crafted JavaScript file.

    CVSS5.0Published7 Oct 2014
  9. 4.7%

    IPython Notebook 0.12 through 1.x before 1.2 does not validate the origin of websocket requests, which allows remote attackers to execute arbitrary code by leveraging knowledge of the kernel id and a crafted page.

    CVSS6.8Published7 Aug 2014
  10. 4.6%

    Off-by-one error in the pcapng_read function in wiretap/pcapng.c in the pcapng file parser in Wireshark 1.10.x before 1.10.13 and 1.12.x before 1.12.4 allows remote attackers to cause a denial of service...

    CVSS5.0Published8 Mar 2015
Every product

All Mageia products we track.

1 products, most vulnerabilities first. Find the ones you run, then open a product to see its versions and exploited flaws.

Precursor Intelligence

Running Mageia? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

Our catalogue lists 22 published vulnerabilities across 1 product and 6 versions from Mageia. The most recent Mageia flaw added to the known-exploited list is CVE-2014-6271, on 28 January 2022.

2 Mageia vulnerabilities are on the list of flaws known to be exploited. The most recently added are CVE-2014-6271 and CVE-2014-7169. The full list is on this page.

Mageia, with 22 published vulnerabilities. Its own page lists the ones known to be exploited.

Create a Precursor Intelligence account and track the Mageia products you run. We match them against every published flaw, give each one a risk score from 0 to 100 and tell you as soon as we spot one that affects you, by email, in the app or by webhook.