Uploaded image for project: 'Application Server 7'
  1. Application Server 7
  2. AS7-5220

tmp/auth/ challenge files are not deleted when access is via a remote client

    XMLWordPrintable

Details

    • Hide

      1) Get the attached jmx client, it came originally from: http://code.google.com/p/jmxquery/downloads/detail?name=jmxquery-1.3-bin.zip&can=2&q=

      2) run a JBoss instance (we used domain mode) with its native management interface accessible to the outside

      3) On a remote server run the following command in a loop
      java -cp ./jmxquery.jar:/opt//jboss/jboss-eap-6-GA/bin/client/jboss-client.jar jmxquery.JMXQuery -U 'service:jmx:remoting-jmx://jbosshost:9999' -username admin -password admin123 -O java.lang:type=Memory -A HeapMemoryUsage -K used

      Change jboss host name, -username and -password as needed

      4) In the domain tmp/auth directory watch the *.challenge files increase

      Show
      1) Get the attached jmx client, it came originally from: http://code.google.com/p/jmxquery/downloads/detail?name=jmxquery-1.3-bin.zip&can=2&q= 2) run a JBoss instance (we used domain mode) with its native management interface accessible to the outside 3) On a remote server run the following command in a loop java -cp ./jmxquery.jar:/opt//jboss/jboss-eap-6-GA/bin/client/jboss-client.jar jmxquery.JMXQuery -U 'service:jmx:remoting-jmx://jbosshost:9999' -username admin -password admin123 -O java.lang:type=Memory -A HeapMemoryUsage -K used Change jboss host name, -username and -password as needed 4) In the domain tmp/auth directory watch the *.challenge files increase
    • Hide

      manually/cronjob clean out the tmp/auth directory

      Show
      manually/cronjob clean out the tmp/auth directory

    Description

      the authentication process that creates temporary files in tmp/auth is not deleting them when a JMX client connects.

      At an extreme, this would be a DOS attack, as the disk could fill up.

      Attachments

        Issue Links

          blocks

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. AS7-5423 Upgrade to Remoting 3.2.8.SP1 or 3.2.11

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved
          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. REM3-156 If a SaslServer or SaslClient is being abandoned dispose should be called to allow clean up.

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. AS7-5326 Upgrade to JBoss SASL 1.0.2.Final

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              darran.lofthouse@redhat.com Darran Lofthouse
              tfonteyn Tom Fonteyne (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: