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

CRLF injection

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

  • CRLF injection

    Hi
    As part of an ongoing security penetration test performed on my server ( Alpha Anywhere Application Server classic ) i still have this issue pending (CRLF Injection)

    The Security Experts recommends to
    - Strip any newline characters before passing content into the HTTP header.
    - Encode the data that you pass into HTTP headers. This will effectively scramble the CR and LF
    codes if the attacker attempts to inject them.

    How can i do that?
    Last edited by WindForce; 11-03-2019, 09:49 AM.

  • #2
    Re: CRLF injection

    Your post was cut off it seems.
    Mike Brown - Contact Me
    Programmatic Technologies, LLC
    Programmatic-Technologies.com
    Independent Developer & Consultant

    Comment


    • #3
      Re: CRLF injection

      Thanks Mike, didn't notice...i edited the post

      Comment


      • #4
        Re: CRLF injection

        ...i'm bumping this since it's stopping the development of a new project for me...

        Here are explanations on CRLF. I'd like to know if someone knows how to prevent this in Alpha Anywhere.


        https://dzone.com/articles/crlf-inje...itting-vulnera
        https://protect2.fireeye.com/v1/url?...g-explained%2F

        Comment


        • #5
          Re: CRLF injection

          As explained in both articles that you linked to, you prevent CRLF header injection by making sure that you only use "safe" values in headers and never directly trust user-supplied input.

          Have you written any custom Xbasic application code that is explicitly setting headers? Most application developers have not and if yo are in this group, this is a non-issue for you. If you are in fact writing custom code to set headers, you will need to make sure that the header values only have safe values in them. If the value is something you've coded directly, this is pretty simple - just don't use a CRLF. If the value is coming from user input, you must remove any potentially malicious characters before setting the header value.

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

          Comment


          • #6
            Re: CRLF injection

            That's the thing Lenny, i haven't written anything of the sort. I even changed my home page to a nearly blank html page and it still doesn't pass.
            Here is an excerpt of the PT report about this issue in my site.
            Code:
            Step-1) Visit https://www.solutions.co.il
            Step-2) Intecept the request using burp suite and send in to the repeater.
            Step-3) Add below payload to the end of the URL:
            
            %3f%0d%0aContent-Length:35%0d%0aX-XSS-
            Protection:0%0d%0a%0d%0a23%0d%0a<svg%20onload=alert(document.domain)>%0d%0a0%0d%0
            a/%2f%2e%2e
            
            Step-4)Forward the request. You will see the HTTP headers successfully get added in the response.

            Comment


            • #7
              Re: CRLF injection

              Originally posted by WindForce View Post
              That's the thing Lenny, i haven't written anything of the sort. I even changed my home page to a nearly blank html page and it still doesn't pass.
              Here is an excerpt of the PT report about this issue in my site.
              Code:
              Step-1) Visit https://www.solutions.co.il
              Step-2) Intecept the request using burp suite and send in to the repeater.
              Step-3) Add below payload to the end of the URL:
              
              %3f%0d%0aContent-Length:35%0d%0aX-XSS-
              Protection:0%0d%0a%0d%0a23%0d%0a<svg%20onload=alert(document.domain)>%0d%0a0%0d%0
              a/%2f%2e%2e
              
              Step-4)Forward the request. You will see the HTTP headers successfully get added in the response.
              I cannot duplicate this. If you can, please enable raw HTTP logging in order to capture the full request and response, then send that log to bugs@alphasoftware.com.

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

              Comment


              • #8
                Re: CRLF injection

                Looks like Alpha has this fixed. Check today's prerelease notes.

                https://aadocuments.s3.amazonaws.com...easeNotes.Html
                Mike Brown - Contact Me
                Programmatic Technologies, LLC
                Programmatic-Technologies.com
                Independent Developer & Consultant

                Comment


                • #9
                  Re: CRLF injection

                  <g>Mike are you fast or what...i've been refreshing the pre-release for hours was still stuck at the Nov.8 version :-)

                  Anyway, i had the cybersecurity company perform the penetration tests while i setup raw http logging. Sent the logs to Lenny, who checked right away and confirmed the vulnerability . A few hours later he sent a mail stating the issue was fixed and it would be in the next pre-release.
                  I can't think of any other dev. tool with such a fast response from the developers themselves.

                  Comment

                  Working...
                  X