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

CSRF Vulnerability...

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

    CSRF Vulnerability...

    The latest PC compliance scan my client received showed three failures on Pages using Dialogs:

    >>Crosssite request forgery vulnerabilities in unathenticated forms can enable attacks such as login CSRF and distributed DoS attacks.
    This is a flaw under the category A5 in the OWASP Top Ten.

    The "recommended" solution is:

    >>In order to facilitate a "transparent but visible" CSRF solution, developers are encouraged to adopt the Synchronizer Token Pattern. This approach requires generating random "challenge" tokens that are associated with the user's current session. These challenge tokens are inserted within the HTML forms and links associated with sensitive serverside operations. When the user wishes to invoke these sensitive operations, the HTTP request should include this challenge token. It is then the responsibility of the server application to verify the existence and correctness of this token.

    As this system has been operational for 3 years without code changes, I am baffled as to "why" this is suddenly an issue.

    Any ideas on how to resolve this?

    Thanks!

    #2
    Re: CSRF Vulnerability...

    Dale,
    V10 is not the latest version and a lot of thinks have changed during the release of V10 as to PC compliance rules.
    At least what you can do is to run the WAS with a vaiid SSL certificate. At the forum search for HartBleed an issue hackers can scam your website even with SSL. You have to replace the openssl drivers with that Apha made available for V11 but it should also work with V10 [btw no guarantee from Alpha or myself] . If your done then check your WAS with a scanner there some free at the internet.
    More info: http://stackoverflow.com/questions/4...rgery-requests

    Eric

    Comment


      #3
      Re: CSRF Vulnerability...

      This in not relaed to Heartbleed...

      The WAS has always used a valid SSL certificate and https. OpenSSL is current - was using 1.01h and updated to 1.01i last night and also updated the SSL Cipher keys per information posted here back in April. hat addressed a different ompliance failure according to the report the client received...

      This issue just came up - the site has been passing PCI compliance monthly prior to August 15...

      I run second instance of WAS on Port 80 which re-directs immediately to the https opening page. The PCI compliance report clearly lists Port 443 as what they are testing because that is how the user accesses te content...

      Comment


        #4
        Re: CSRF Vulnerability...

        Hi Dale,

        Have you ever found a solution to this. I am having csrf issues now in 2016.

        Thanks,
        Simone

        Comment


          #5
          Re: CSRF Vulnerability...

          Simone:

          Sorry, there is no solution because the SSL Library in Version 10.5 is obsolete and not supported. You have to upgrade to V11 or better to use the current SSL library that supports disabling SSL in favor of TLS.

          Comment


            #6
            Re: CSRF Vulnerability...

            Thanks, Dale

            I must be having a different issue, then. I am using V12!
            For some reason our web application firewall is flagging requests as csrf issues.

            Simone

            Comment


              #7
              Re: CSRF Vulnerability...

              That is strange because V12 has the code needed to create the random tokens on Dialog boxes, something V10.5 lacked. What firewall and what is the actual text of the message?

              Sorry, this is an old thread and I was confusing it with the SSL issue thread I also started a long time ago.

              Comment


                #8
                Re: CSRF Vulnerability...

                Hi Dale,

                I started a thread, two days ago, describing the problem in more detail:
                http://www.alphasoftware.com/alphafo...equest+forgery

                There is a screenshot there showing the log message from the web application firewall. The firewall vendor is A10.

                I would really appreciate any insights you may have about this. So far nobody has replied and I don't quite know attack the problem.

                Thanks!
                Simone

                Comment

                Working...
                X