ubuntu-cve-2019-1549
Vulnerability from osv_ubuntu
Published
2019-09-10 17:15
Modified
2026-04-22 07:38
Summary
Details

OpenSSL 1.1.1 introduced a rewritten random number generator (RNG). This was intended to include protection in the event of a fork() system call in order to ensure that the parent and child processes did not share the same RNG state. However this protection was not being used in the default case. A partial mitigation for this issue is that the output from a high precision timer is mixed into the RNG state so the likelihood of a parent and child process sharing state is significantly reduced. If an application already calls OPENSSL_init_crypto() explicitly using OPENSSL_INIT_ATFORK then this problem does not occur at all. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c).

Severity
5.3 (Medium)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
N/A (UNKNOWN)
low
References
To clipboard 

{
  "affected": [
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "libssl1.1",
            "binary_version": "1.1.1-1ubuntu2.1~18.04.6"
          },
          {
            "binary_name": "openssl",
            "binary_version": "1.1.1-1ubuntu2.1~18.04.6"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:18.04:LTS",
        "name": "openssl",
        "purl": "pkg:deb/ubuntu/openssl@1.1.1-1ubuntu2.1~18.04.6?arch=source\u0026distro=bionic"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.1.1-1ubuntu2.1~18.04.6"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "1.0.2g-1ubuntu13",
        "1.0.2g-1ubuntu14",
        "1.0.2n-1ubuntu1",
        "1.1.0g-2ubuntu1",
        "1.1.0g-2ubuntu2",
        "1.1.0g-2ubuntu3",
        "1.1.0g-2ubuntu4",
        "1.1.0g-2ubuntu4.1",
        "1.1.0g-2ubuntu4.3",
        "1.1.1-1ubuntu2.1~18.04.1",
        "1.1.1-1ubuntu2.1~18.04.2",
        "1.1.1-1ubuntu2.1~18.04.3",
        "1.1.1-1ubuntu2.1~18.04.4",
        "1.1.1-1ubuntu2.1~18.04.5"
      ]
    }
  ],
  "aliases": [],
  "details": "OpenSSL 1.1.1 introduced a rewritten random number generator (RNG). This was intended to include protection in the event of a fork() system call in order to ensure that the parent and child processes did not share the same RNG state. However this protection was not being used in the default case. A partial mitigation for this issue is that the output from a high precision timer is mixed into the RNG state so the likelihood of a parent and child process sharing state is significantly reduced. If an application already calls OPENSSL_init_crypto() explicitly using OPENSSL_INIT_ATFORK then this problem does not occur at all. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c).",
  "id": "UBUNTU-CVE-2019-1549",
  "modified": "2026-04-22T07:38:49Z",
  "published": "2019-09-10T17:15:00Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2019-1549"
    },
    {
      "type": "REPORT",
      "url": "https://www.openssl.org/news/secadv/20190910.txt"
    },
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-4376-1"
    },
    {
      "type": "REPORT",
      "url": "https://www.cve.org/CVERecord?id=CVE-2019-1549"
    }
  ],
  "related": [
    "USN-4376-1"
  ],
  "schema_version": "1.7.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
      "type": "CVSS_V3"
    },
    {
      "score": "low",
      "type": "Ubuntu"
    }
  ],
  "upstream": [
    "CVE-2019-1549"
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.