usn-6913-2
Vulnerability from osv_ubuntu
Published
2024-07-31 18:01
Modified
2026-06-25 10:46
Summary
php-cas vulnerability
Details

USN-6913-1 fixed CVE-2022-39369 for Ubuntu 20.04 LTS and Ubuntu 22.04 LTS. This update provides the corresponding fix for Ubuntu 16.04 LTS.

Original advisory details:

Filip Hejsek discovered that phpCAS was using HTTP headers to determine the service URL used to validate tickets. A remote attacker could possibly use this issue to gain access to a victim's account on a vulnerable CASified service.

This security update introduces an incompatible API change. After applying this update, third party applications need to be modified to pass in an additional service base URL argument when constructing the client class.

For more information please refer to the section "Upgrading 1.5.0 -> 1.6.0" of the phpCAS upgrading document:

https://github.com/apereo/phpCAS/blob/master/docs/Upgrading

References
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "cves_map": {
          "cves": [
            {
              "id": "CVE-2022-39369",
              "severity": [
                {
                  "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H",
                  "type": "CVSS_V3"
                },
                {
                  "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H",
                  "type": "CVSS_V3"
                },
                {
                  "score": "medium",
                  "type": "Ubuntu"
                }
              ]
            }
          ],
          "ecosystem": "Ubuntu:Pro:16.04:LTS"
        }
      },
      "ecosystem_specific": {
        "availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
        "binaries": [
          {
            "binary_name": "php-cas",
            "binary_version": "1.3.3-2ubuntu1+esm1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:Pro:16.04:LTS",
        "name": "php-cas",
        "purl": "pkg:deb/ubuntu/php-cas@1.3.3-2ubuntu1+esm1?arch=source\u0026distro=esm-apps/xenial"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.3.3-2ubuntu1+esm1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "1.3.3-1",
        "1.3.3-2",
        "1.3.3-2ubuntu1"
      ]
    }
  ],
  "aliases": [],
  "details": "USN-6913-1 fixed CVE-2022-39369 for Ubuntu 20.04 LTS and Ubuntu 22.04 LTS.\nThis update provides the corresponding fix for Ubuntu 16.04 LTS.\n\nOriginal advisory details:\n\nFilip Hejsek discovered that phpCAS was using HTTP headers to determine\nthe service URL used to validate tickets. A remote attacker could\npossibly use this issue to gain access to a victim\u0027s account on a\nvulnerable CASified service.\n\nThis security update introduces an incompatible API change. After applying\nthis update, third party applications need to be modified to pass in an\nadditional service base URL argument when constructing the client class.\n\nFor more information please refer to the section\n\"Upgrading 1.5.0 -\u003e 1.6.0\" of the phpCAS upgrading document:\n\nhttps://github.com/apereo/phpCAS/blob/master/docs/Upgrading\n",
  "id": "USN-6913-2",
  "modified": "2026-06-25T10:46:26Z",
  "published": "2024-07-31T18:01:51Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-6913-2"
    },
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2022-39369"
    }
  ],
  "related": [],
  "schema_version": "1.7.0",
  "summary": "php-cas vulnerability",
  "upstream": [
    "UBUNTU-CVE-2022-39369"
  ]
}



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.