Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Critical Security Flaw? HEAD Command

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Critical Security Flaw? HEAD Command

    This morning I was checking my logs and came across hundreds of these:

    74.86.158.107 - - [22/Jul/2013:01:11:38 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643

    WHOIS reports:
    network:Organization;I:Buzpark Ltd.
    network:Street-Address:Akyap Sitesi D Blok D8
    network:City:Istanbul
    network:Postal-Code:34464
    network:Country-Code:TR

    The following white paper describes the HEAD command and how it may be used as an exploit:
    https://www.owasp.org/index.php/Test...WASP-CM-008%29

    QUESTION:
    Is there a config file where I can allow GET and POST but disallow other commands like TRACE, HEAD, DELETE, OPTIONS, PUT, etc?
    Rapid Development, Training, Support
    http://data2web.network
    903-740-2549

  • #2
    Re: Critical Security Flaw? HEAD Command

    Originally posted by mvaughn View Post
    This morning I was checking my logs and came across hundreds of these:

    74.86.158.107 - - [22/Jul/2013:01:11:38 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643

    WHOIS reports:
    network:Organization;I:Buzpark Ltd.
    network:Street-Address:Akyap Sitesi D Blok D8
    network:City:Istanbul
    network:Postal-Code:34464
    network:Country-Code:TR

    The following white paper describes the HEAD command and how it may be used as an exploit:
    https://www.owasp.org/index.php/Test...WASP-CM-008%29

    QUESTION:
    Is there a config file where I can allow GET and POST but disallow other commands like TRACE, HEAD, DELETE, OPTIONS, PUT, etc?
    feedback from owasp.org :

    If you get a "405 Method not allowed" or "501 Method Unimplemented", the application/framework/language/system/firewall is working correctly. If a "200" response code comes back, and the response contains no body, it's likely that the application has processed the request without authentication or authorization and further testing is warranted.

    i suspect somebody in Turky is running a reverse alphascript from this orginal site https://ablejobs.us/emp-login.a5w
    in the WAS disallow the ip from TKy in your that will fix the false login attempt.
    restart the was.
    Last edited by bea2701; 07-23-2013, 09:48 AM.

    Comment


    • #3
      Re: Critical Security Flaw? HEAD Command

      Thank you Eric for your reply. I had already firewalled that IP.

      This incident got me wondering.
      Alpha 5 is strictly a database platform, and as such, would be a tempting target for anyone wanting data.

      I would be very surprised if there were not already exploits for it in the wild.

      Comments, anyone?
      Rapid Development, Training, Support
      http://data2web.network
      903-740-2549

      Comment


      • #4
        Re: Critical Security Flaw? HEAD Command

        Eric, I'm curious. How did you determine that https://ablejobs.us/emp-login.a5w was the original site? Of course you are correct, but I made no mention of the domain in my above post.
        Rapid Development, Training, Support
        http://data2web.network
        903-740-2549

        Comment


        • #5
          Re: Critical Security Flaw? HEAD Command

          How to find a web page? Check this.

          Comment


          • #6
            Re: Critical Security Flaw? HEAD Command

            You cracked me up, lol. I needed that this morning.
            Wow, I'm actually first on the search page! I finally made it! lol.
            Rapid Development, Training, Support
            http://data2web.network
            903-740-2549

            Comment


            • #7
              Re: Critical Security Flaw? HEAD Command

              A HEAD request is exactly the same as a GET request, except that only the headers are sent back to the client. It is processed exactly the same way, so there is nothing at all being bypassed. The security framework is fully enforced and this is not an avenue of exploit.

              The Application Server only supports GET, POST, HEAD and OPTIONS. There is no setting to disable individual methods.

              Lenny Forziati
              Vice President, Internet Products and Technical Services
              Alpha Software Corporation

              Comment


              • #8
                Re: Critical Security Flaw? HEAD Command

                Thank you Lenny, its good to know what commands are accepted and processed.
                But have you any idea what this guy is doing?

                74.86.158.106 - - [22/Jul/2013:00:41:37 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.106 - - [22/Jul/2013:00:46:37 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.106 - - [22/Jul/2013:00:51:37 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.106 - - [22/Jul/2013:00:56:37 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.107 - - [22/Jul/2013:01:01:37 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.107 - - [22/Jul/2013:01:06:37 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                5.10.83.49 - - [22/Jul/2013:01:07:09 -0500] "GET / HTTP/1.1" 403 182
                74.86.158.107 - - [22/Jul/2013:01:11:38 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.106 - - [22/Jul/2013:01:16:37 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.106 - - [22/Jul/2013:01:21:37 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.106 - - [22/Jul/2013:01:26:38 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                5.10.83.48 - - [22/Jul/2013:01:28:24 -0500] "GET / HTTP/1.1" 403 182
                74.86.158.106 - - [22/Jul/2013:01:31:37 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.107 - - [22/Jul/2013:01:36:38 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.107 - - [22/Jul/2013:01:41:38 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.107 - - [22/Jul/2013:01:46:38 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.106 - - [22/Jul/2013:01:51:38 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.107 - - [22/Jul/2013:01:56:38 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.107 - - [22/Jul/2013:02:01:38 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.107 - - [22/Jul/2013:02:06:38 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.107 - - [22/Jul/2013:02:11:38 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.107 - - [22/Jul/2013:02:16:38 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.106 - - [22/Jul/2013:02:21:38 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.107 - - [22/Jul/2013:02:26:38 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.107 - - [22/Jul/2013:02:36:39 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.107 - - [22/Jul/2013:02:41:39 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.106 - - [22/Jul/2013:02:46:39 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.107 - - [22/Jul/2013:02:51:39 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.107 - - [22/Jul/2013:02:56:39 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.106 - - [22/Jul/2013:03:01:39 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.106 - - [22/Jul/2013:03:06:39 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.107 - - [22/Jul/2013:03:11:39 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.106 - - [22/Jul/2013:03:16:39 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.106 - - [22/Jul/2013:03:21:39 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.106 - - [22/Jul/2013:03:26:39 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.106 - - [22/Jul/2013:03:31:39 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.106 - - [22/Jul/2013:03:36:39 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.107 - - [22/Jul/2013:03:41:39 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.107 - - [22/Jul/2013:03:46:39 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.107 - - [22/Jul/2013:03:51:39 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.106 - - [22/Jul/2013:03:56:39 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.106 - - [22/Jul/2013:04:01:39 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.107 - - [22/Jul/2013:04:06:39 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.107 - - [22/Jul/2013:04:11:39 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                74.86.158.106 - - [22/Jul/2013:04:16:39 -0500] "HEAD /emp-login.a5w HTTP/1.1" 200 17643
                ad infinitum...
                Rapid Development, Training, Support
                http://data2web.network
                903-740-2549

                Comment


                • #9
                  Re: Critical Security Flaw? HEAD Command

                  google one of the ip addresses listed and see what you find......


                  ie 74.86.158.106

                  uptimerobot
                  Al Buchholz
                  Bookwood Systems, LTD
                  Weekly QReportBuilder Webinars Thursday 1 pm CST

                  Occam's Razor - KISS
                  Normalize till it hurts - De-normalize till it works.
                  Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
                  When we triage a problem it is much easier to read sample systems than to read a mind.
                  "Make it as simple as possible, but not simpler."
                  Albert Einstein

                  http://www.iadn.com/images/media/iadn_member.png

                  Comment


                  • #10
                    Re: Critical Security Flaw? HEAD Command

                    You can probably assume it's a bot. Being a login page, it's probably trying to log in.

                    I periodically see a rash of requests like this. Usually GET requests. A bunch of them. All in a row. They never request a POST. And, on occasion, such activity has coincided with a WAS "out of memory" failure. I keep a special bad bot list in my firewall for just such an occasion. You can block the entire IP range from 74.86.158.0 to 74.86.158.255.

                    I recommend blocking at the firewall level. It will handle the whole machine, not just the WAS. And, if you're me running 5 instances of the WAS on the same server, it's considerably easier to set this up in one location instead of... many.
                    Alpha Anywhere latest pre-release

                    Comment


                    • #11
                      Re: Critical Security Flaw? HEAD Command

                      I use uptime robot. It's a service that basically pings to see if your server is up every X minutes. http://www.uptimerobot.com/

                      Comment


                      • #12
                        Re: Critical Security Flaw? HEAD Command

                        Yup, you are quite right.
                        I had forgotten that I use uptime robot.
                        I chose the login page because it is an a5w page.
                        After firewalling the ip I got flooded with server down emails, lol.
                        But if anything, I learned what commands the server supported and to google the ip.
                        I should have caught that.
                        Thanks to all!
                        Rapid Development, Training, Support
                        http://data2web.network
                        903-740-2549

                        Comment


                        • #13
                          Re: Critical Security Flaw? HEAD Command

                          You may want to consider using a smaller and lighter-weight A5W page for the health check. This could reduce the load on your server caused by the checking.

                          Something as simple as the following would be enough to verify that the server is online and processing A5W pages:
                          Code:
                          <%a5
                          Response.Write("Hello World")
                          %>
                          If needed for your application, you could also add some Xbasic to check a back-end database server too.

                          Lenny Forziati
                          Vice President, Internet Products and Technical Services
                          Alpha Software Corporation

                          Comment


                          • #14
                            Re: Critical Security Flaw? HEAD Command

                            Lenny -

                            Seems to me that Xbasic would need to be a UDF in an AEX with OPTION ENCRYPTED_TOKENS to insure security?

                            And would the page only return something if the database server responded properly? So a little more like this maybe?

                            Code:
                            <%a5
                            if ServerHealthCheck() then
                                Response.Write("Hello World")
                            end if
                            %>
                            I was about to roll my own uptime monitoring, but this looks like a good alternative, which is why I'm asking.
                            -Steve
                            sigpic

                            Comment

                            Working...
                            X