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

Security Issue Cross Site scripting

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

    Security Issue Cross Site scripting

    Hello, there have been some vunurabilities found in our web application developed through alpha five .One of them is the Cross Site scripting.

    Description
    The root cause of CrossSite Scripting (XSS) is a failure to filter hazardous characters from web application input and output. The two programming practice you can use to guard against Cross-Site Scripting are:
    1. Validate Input
    2. Encode output.

    Is there is an easy way to validate the input right from the development tool or there is some code that will need to be written i.e i want to validate if special characters are inputted and give user some message that it is not allowed.

    Thanks

    Sunny

    #2
    Re: Security Issue Cross Site scripting

    Yes, see the Web Security > Configure Security and look for Password Validation Rules. You can prohibit various entries.

    I know a couple guys that want to do a security review of their site also, can you share who you used and what other security risks they found?
    Steve Wood
    See my profile on IADN

    Comment


      #3
      Re: Security Issue Cross Site scripting

      Steve ,

      Here are others .

      ** If the web application returns an HTTP 200 OK response, with the session ID set to the value the attack has injected, the site is vulnerable to session fixation.
      Session IDs are not updated when the same user logs out/session expires, and then logs back in.

      ** same request was sent twice in different sessions and the same response was received. This shows that none of the parameters are dynamic (session identifiers are sent only in cookies) and therefore that the application is vulnerable to this issue. It is possible to steal or manipulate customer session and cookies, which might be used to impersonate a legitimate user, allowing the hacker to view or alter user records, and to perform transactions as that user.

      ** If secure is not specified, a cookie is considered safe to be sent in the clear over unsecured channels. These cookies may the be captured by an attacker and used to hijack a user session.

      Comment


        #4
        Re: Security Issue Cross Site scripting

        I sent a private email to the only two guys who would be able to answer these questions. I don't know if your study included using 'protected session variables' which cannot be set by the URL. At a minimum, this kind of detailed testing should lead to best practices to avoid what can be avoided.
        Steve Wood
        See my profile on IADN

        Comment


          #5
          Re: Security Issue Cross Site scripting

          Thanks Steve ,

          Over the coming two weeks I have to fix all these issues or give an estimate to the testing team as to how much time it will take to fix them .

          There are some other issues as well , I will share them as well .

          Thanks

          Sunny .

          Comment


            #6
            Re: Security Issue Cross Site scripting

            Did you get the XSS issues resolved. I'm running into the same issues regarding PCI compliance.

            Thanks
            Anthony

            Comment


              #7
              Re: Security Issue Cross Site scripting

              There have been a number of changes and security changes made since V9. Session management has been totally revamped and the way in which session IDs are generated and used is significantly different. None of the issues raised in this thread exist in V11. If your specific issues differ from those already listed, detail them and I will tell you if they too have been addressed.

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

              Comment


                #8
                Re: Security Issue Cross Site scripting

                Here is the wording from the PCI scan:

                "THREAT:
                Your Web server/application does not filter script embedding from links displayed on a server's Web site.


                A malicious user can exploit this vulnerability to cause JavaScript commands or embedded scripts to be executed by any user who clicks on the
                hyperlink. Upon clicking the hyperlink, your Web server will generate an error message including the specified or embedded script. The specified or
                embedded script is executed in the client's browser and treated as content originating from the target server returning the error message (even
                though the scripting may have originated from another site entirely).


                IMPACT:
                By exploiting this vulnerability, malicious scripts can be executed in the client's browser.


                SOLUTION:
                Any Web application on the server may be affected by this vulnerability. To prevent cross-site scripting attacks from occurring, web developers
                should use static pages whenever possible and sanitize input / output.
                "
                I've also attached the full document.
                Thanks,
                Anthony
                Attached Files

                Comment


                  #9
                  Re: Security Issue Cross Site scripting

                  Anthony, after working on your support incident, reviewing the report in detail, reviewing the application itself which you submitted, and performing varied testing, I can verify that the scanner used to generate this report has flagged a false positive. There is no XSS exploit here in V11.

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

                  Comment


                    #10
                    Re: Security Issue Cross Site scripting

                    Hi Lenny,
                    Thank you for checking. I will work with our PCI consultants to get this cleared.

                    Thanks,
                    Anthony Ward

                    Comment

                    Working...
                    X