Security hole in Zabbix: it uses unprotected SYSV shared memory for some reason.

XMLWordPrintable

    • Type: Incident report
    • Resolution: Fixed
    • Priority: Critical
    • 1.8.5
    • Affects Version/s: 1.8.4
    • Component/s: None
    • None

      Security hole in Zabbix: it uses unprotected SYSV shared memory for some reason.

      Perhaps we should not give write permissions for the other processes to the Zabbix memory segments.

            Assignee:
            Unassigned
            Reporter:
            Igor Danoshaites (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: