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

Recent SQL Injection attacks

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

    Recent SQL Injection attacks

    Just a notice that I have had several SQL Injection attacks on the iadn.com website in the last week, all from several Netherlands IP address. It has nothing to do with the site being Alpha. But you should review your logs occasionally and have a means to block by IP address (You can use the one built in to Alpha web server, but it is better to use a 3rd party tool because although Alpha's blocks access, each hit still takes up web server resources, and because you have to stop-start the Alpha server for the block to take effect).

    Here is a summary of 'how to prevent' sql injection attacks from website: https://www.codeproject.com/Articles...on-How-to-Prev
    • Encrypt sensitive data.
    • Access the database using an account with the least privileges necessary.
    • Install the database using an account with the least privileges necessary.
    • Ensure that data is valid.
    • Do a code review to check for the possibility of second-order attacks.
    • Use parameterised queries.
    • Use stored procedures.
    • Re-validate data in stored procedures.
    • Ensure that error messages give nothing away about the internal architecture of the application or the database.


    Here is an example of how injectoin looks in the Alpha web server access log:

    185.92.73.107 - - [05/Nov/2017:14:19:53 -0600] "GET /events.a5w?A5WSessionId=f7587af9da034468b1e4202d16e9ad4d&qtsT%3D3276%20AND%201%3D1%20UNION%20ALL%20SELECT%201%2CNULL%2C%27%3Cscript%3Ealert%28%22XSS%22%29%3C%2Fscript%3E%27%2Ctable_name%20FROM%20information_schema.tables%20WHERE%202%3E1--%2F%2A%2A%2F%3B%20EXEC%20xp_cmdshell%28%27cat%20..%2F..%2F..%2Fetc%2Fpasswd%27%29%23 HTTP/1.1" 200 60385
    185.92.73.107 - - [05/Nov/2017:14:19:58 -0600] "GET /events.a5w?A5WSessionId=f7587af9da034468b1e4202d16e9ad4d HTTP/1.1" 200 59573
    185.92.73.107 - - [05/Nov/2017:14:20:02 -0600] "GET /events.a5w?A5WSessionId=f7587af9da034468b1e4202d16e9ad4d%27%2C%22..%2C%29%2C.%28 HTTP/1.1" 200 59655
    185.92.73.107 - - [05/Nov/2017:14:20:05 -0600] "GET /events.a5w?A5WSessionId=f7587af9da034468b1e4202d16e9ad4d%27lnVaEb%3C%27%22%3EUCFjBq HTTP/1.1" 200 59665
    185.92.73.107 - - [05/Nov/2017:14:20:16 -0600] "GET /events.a5w?A5WSessionId=f7587af9da034468b1e4202d16e9ad4d%29%20AND%206423%3D3998%20AND%20%286707%3D6707 HTTP/1.1" 200 59725
    185.92.73.107 - - [05/Nov/2017:14:20:22 -0600] "GET /events.a5w?A5WSessionId=f7587af9da034468b1e4202d16e9ad4d%29%20AND%201860%3D1860%20AND%20%281962%3D1962 HTTP/1.1" 200 59725
    185.92.73.107 - - [05/Nov/2017:14:20:26 -0600] "GET /events.a5w?A5WSessionId=f7587af9da034468b1e4202d16e9ad4d%29%20AND%204046%3D3998%20AND%20%289833%3D9833 HTTP/1.1" 200 59725
    185.92.73.107 - - [05/Nov/2017:14:20:30 -0600] "GET /events.a5w?A5WSessionId=f7587af9da034468b1e4202d16e9ad4d%20AND%203636%3D8661 HTTP/1.1" 200 59641
    185.92.73.107 - - [05/Nov/2017:14:20:35 -0600] "GET /events.a5w?A5WSessionId=f7587af9da034468b1e4202d16e9ad4d%20AND%201860%3D1860 HTTP/1.1" 200 59641
    185.92.73.107 - - [05/Nov/2017:14:20:38 -0600] "GET /events.a5w?A5WSessionId=f7587af9da034468b1e4202d16e9ad4d%20AND%206370%3D5443 HTTP/1.1" 200 59641
    185.92.73.107 - - [05/Nov/2017:14:20:42 -0600] "GET /events.a5w?A5WSessionId=f7587af9da034468b1e4202d16e9ad4d%27%29%20AND%203672%3D8377%20AND%20%28%27GUvw%27%3D%27GUvw HTTP/1.1" 200 59765
    Steve Wood
    See my profile on IADN


    #2
    Re: Recent SQL Injection attacks

    A minor point Steve, but you should not need to restart the Application Server to apply a block on a new IP address. While that was true in previous versions, Alpha Anywhere picks these configuration changes up on the fly.

    That said, I agree completely with your assertion that the Application Server itself is not the best place to do this blocking. In fact, this is something I discussed in my security presentation at DevCon a couple of weeks ago. The functionality is there in case you have no other mechanism available, but it is very inefficient to be doing IP restrictions at this level of the network stack. IP restrictions are much more efficiently handled in a firewall or other layer 3 device/software.

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

    Comment


      #3
      Re: Recent SQL Injection attacks

      I am using a product by BeeThink to block countries and by blacklist. It works, but looks like it has not been updated since DOS days.
      Steve Wood
      See my profile on IADN

      Comment


        #4
        Re: Recent SQL Injection attacks

        I would add to the list also that do not use SQL if you do not especially need it. Flat file web sites thanks to json are more and more popular all the time.
        Also use just service providers that have an external firewall a standard feature, like Leaseweb USA cloud and AWS.
        Also with classic AA server use reverse proxy and bind AA server to localhost.

        Also is good to notice that they do "scan"/"ping" normally to an IP address and not to an domain name. So bind your IP address to an empty web site. You need to use reverse proxy with multi host support to get this done with classic aa server.

        Comment


          #5
          Re: Recent SQL Injection attacks

          Steve,

          That ip adres is located at FoxCloud LLP located Netherlands Amsterdam that is a cloudprovider but the user is from Cyprus

          hope helps

          Comment


            #6
            Re: Recent SQL Injection attacks

            Yes saw that. I am using blacklists and blocking some countries. But one cannot just blindly block by country. I track login attempts at my site as well, and every single day I get attempted logins from Russia and China domains. Recently for a B2B client, I totally restriced all public domains from registering (yahoo, gmail, yandex, etc). I cannot do that in my case because many independent developers and small businesses use public domain email addresses.
            Steve Wood
            See my profile on IADN

            Comment

            Working...
            X