Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-1310

DISA STIG finding V-230486 requires disabling chrony 'cmdport' even if the port is only listening on 'lo' (::1 / 127.0.0.1)

Linking RHIVOS CVEs to...Migration: Automation ...Sync from "Extern...XMLWordPrintable

    • None
    • None
    • rhel-security-compliance
    • ssg_security
    • None
    • False
    • False
    • Hide

      None

      Show
      None
    • No
    • None
    • None
    • None
    • If docs needed, set a value
    • None
    • 57,005

      Description of problem:

      DISA STIG finding V-230486 requires disabling chrony 'cmdport 0' even if the port is only listening on 'lo' (::1 / 127.0.0.1)
      And this prevents local stats verification using 'chronyc' from an unprivileged user (for monitoring)

      Version-Release number of selected component (if applicable):

      How reproducible:

      Always

      Steps to Reproduce:

      1. default chrony install

      1. yum install chrony
      2. systemctl start chronyd
        2. with an unprivileged user:
        $ chronyc sources
        $ chronyc delete <ntp_source_from_above>
        3. add cmdport 0
      3. echo "cmdport 0" >> /etc/chrony.conf
      4. systemctl restart chronyd
        4. with an unprivileged user again
        $ chronyc sources

      Actual results:

      2. $ chronyc sources
      <source output>
      $ chronyc delete <ntp_source_from_above>
      501 Not authorised

      4. $ chronyc sources
      506 Cannot talk to daemon

      Expected results:

      The expected results is that the STIG verify the actual interface where the cmdport is listening to, in order to either pass or not the verification.
      Maybe this is something to discuss with DISA

      Additional info:

      Unprivileged user contacting chronyd over port 323 via localhost interface cannot modify settings.

      JGamba

              vpolasek@redhat.com Vojtech Polasek
              rhn-support-jgamba Juan Gamba
              Vojtech Polasek Vojtech Polasek
              SSG Security QE SSG Security QE
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: