usn-5259-3
Vulnerability from osv_ubuntu
Published
2022-05-11 00:25
Modified
2026-06-25 10:46
Summary
cron regression
Details

USN-5259-1 and USN-5259-2 fixed vulnerabilities in Cron. Unfortunately that update was incomplete and could introduce a regression. This update fixes the problem.

We apologize for the inconvenience.

Original advisory details:

It was discovered that the postinst maintainer script in Cron unsafely handled file permissions during package install or update operations. An attacker could possibly use this issue to perform a privilege escalation attack. (CVE-2017-9525)

Florian Weimer discovered that Cron incorrectly handled certain memory operations during crontab file creation. An attacker could possibly use this issue to cause a denial of service. (CVE-2019-9704)

It was discovered that Cron incorrectly handled user input during crontab file creation. An attacker could possibly use this issue to cause a denial of service. (CVE-2019-9705)

It was discovered that Cron contained a use-after-free vulnerability in its force_rescan_user function. An attacker could possibly use this issue to cause a denial of service. (CVE-2019-9706)


{
  "affected": [
    {
      "database_specific": {
        "cves_map": {
          "cves": [
            {
              "id": "CVE-2017-9525",
              "severity": [
                {
                  "score": "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H",
                  "type": "CVSS_V3"
                },
                {
                  "score": "low",
                  "type": "Ubuntu"
                }
              ]
            }
          ],
          "ecosystem": "Ubuntu:Pro:16.04:LTS"
        }
      },
      "ecosystem_specific": {
        "availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
        "binaries": [
          {
            "binary_name": "cron",
            "binary_version": "3.0pl1-128ubuntu2+esm2"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:Pro:16.04:LTS",
        "name": "cron",
        "purl": "pkg:deb/ubuntu/cron@3.0pl1-128ubuntu2+esm2?arch=source\u0026distro=esm-infra/xenial"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "3.0pl1-128ubuntu2+esm2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "3.0pl1-127ubuntu1",
        "3.0pl1-128ubuntu1",
        "3.0pl1-128ubuntu2",
        "3.0pl1-128ubuntu2+esm1"
      ]
    },
    {
      "database_specific": {
        "cves_map": {
          "cves": [
            {
              "id": "CVE-2017-9525",
              "severity": [
                {
                  "score": "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H",
                  "type": "CVSS_V3"
                },
                {
                  "score": "low",
                  "type": "Ubuntu"
                }
              ]
            }
          ],
          "ecosystem": "Ubuntu:18.04:LTS"
        }
      },
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "cron",
            "binary_version": "3.0pl1-128.1ubuntu1.2"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:18.04:LTS",
        "name": "cron",
        "purl": "pkg:deb/ubuntu/cron@3.0pl1-128.1ubuntu1.2?arch=source\u0026distro=bionic"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "3.0pl1-128.1ubuntu1.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "3.0pl1-128ubuntu5",
        "3.0pl1-128.1ubuntu1",
        "3.0pl1-128.1ubuntu1.1"
      ]
    }
  ],
  "aliases": [],
  "details": "USN-5259-1 and USN-5259-2 fixed vulnerabilities in Cron. Unfortunately\nthat update was incomplete and could introduce a regression. This update\nfixes the problem.\n\nWe apologize for the inconvenience.\n\nOriginal advisory details:\n\n It was discovered that the postinst maintainer script in Cron unsafely\n handled file permissions during package install or update operations.\n An attacker could possibly use this issue to perform a privilege\n escalation attack. (CVE-2017-9525)\n \n Florian Weimer discovered that Cron incorrectly handled certain memory\n operations during crontab file creation. An attacker could possibly use\n this issue to cause a denial of service. (CVE-2019-9704)\n \n It was discovered that Cron incorrectly handled user input during crontab\n file creation. An attacker could possibly use this issue to cause a denial\n of service. (CVE-2019-9705)\n \n It was discovered that Cron contained a use-after-free vulnerability in\n its force_rescan_user function. An attacker could possibly use this issue\n to cause a denial of service. (CVE-2019-9706)\n",
  "id": "USN-5259-3",
  "modified": "2026-06-25T10:46:03Z",
  "published": "2022-05-11T00:25:41Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-5259-3"
    },
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2017-9525"
    },
    {
      "type": "REPORT",
      "url": "https://launchpad.net/bugs/1971895"
    }
  ],
  "related": [],
  "schema_version": "1.7.0",
  "summary": "cron regression",
  "upstream": [
    "UBUNTU-CVE-2017-9525"
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…