<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-04T21:05:45.605401+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2022-0860</id>
    <title>CVE-2022-0860 — Improper Authorization in cobbler/cobbler</title>
    <updated>2026-10-04T21:05:45.607076+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> cobbler/cobbler</p>
<p>Improper Authorization in GitHub repository cobbler/cobbler prior to 3.3.2.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2022-0860"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-mcg6-h362-cmq5</id>
    <title>GHSA-mcg6-h362-cmq5 — Improper Authorization in cobbler</title>
    <updated>2026-10-04T21:05:45.607126+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: cobbler</p>
<p>### Impact</p>
<p>If PAM is correctly configured and a user account is set to expired, the expired user-account is still able to successfully log into Cobbler in all places (Web UI, CLI &amp; XMLRPC-API).</p>
<p>The same applies to user accounts with passwords set to be expired.</p>
<p>### Patches</p>
<p>There is a patch for the latest Cobbler `3.3.2` available, however a backport will be done for `3.2.x`.</p>
<p>### Workarounds</p>
<p>- Delete expired accounts which are able to access Cobbler via PAM.
- Use `chage -l &lt;username&gt;` to lock the account. If the account has SSH-Keys attached then remove them completely.</p>
<p>### References</p>
<p>- Originally discovered by @ysf at https://www.huntr.dev/bounties/c458b868-63df-414e-af10-47e3745caa1d/</p>
<p>### How to test if my Cobbler instance is affected?</p>
<p>The following `pytest` test assumes that your PAM setup is correct. In case the added user is not able to login, this test does not make sense to be executed.</p>
<p>```python
def test_pam_login_with_expired_user():
    # Arrange
    # create pam testuser
    test_username = "expired_user"
    test_password = "password"
    test_api = CobblerAPI()
    subprocess_1 = subprocess.run(
        ["perl", "-e", "'print crypt(\"%s\", \"%s\")'" % (test_username, test_password)],
        stdout=subprocess.PIPE
    )
    subprocess.run(["useradd", "-p", subprocess_1.stdout, test_username])
    # change user to be expired
    subprocess.run(["chage", "-E0", test_username])</p>
<p># Act
    result = pam.authenticate(test_api, test_username, test_passwo…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-mcg6-h362-cmq5"/>
  </entry>
</feed>
