Fix : AWS ElasticBean Deployment fails for Rails Application

There is always an issue with Amazon Web Services ElasticBean while deploying applications and always a scary part. It was a cakewalk on Heroku hosting platform but it's nightmare here and wastes days

TheRails Application use Puma as default server, recently it has updated to 5.2.2 at the time of writing this post.

During the recent deployments to AWS elasticbean all have been failing, The main reason is the Gem File isn't being obeyed.

The specified version of the Puma isn't being instaled by the AWS serves when A revolution for server

I decided to go back to Django again. You can read this post to encounter what all I encountered duint the deployments of Django Application.

So going back to Rails. Everything has been installed properly except the Puma server.

I specified 4.3.2 in my Gem File but AWS was installing the 5.2.2. And all the Load Balancers have been showing the status of 502 or 400. The Server health is shown as degraded or severe.

Here are the steps to overcome this issue.

1. In you Gem file, delete the line gem 'puma'.

2. Put this code gem 'passenger'.

3. Run bundle install.

Push it to your AWS Code Commit and run eb deploy

Comments

$1337 YouTube Community (Posts) bug

YouTube Community is a feature that is only available for Channels with 1. Verified Phone numbers 2. A significant history, more content for years. In the early June I started hunting for Security flaws on YouTube I was roaming around the features but most of the places have been found secure or already potential features had the bugs fixes in place. The Community Tab is now Posts So, I thought to exploit Youtube Community feature. I was trying to delete the Posts using IDOR attacks but it didn't work I was tired of trying various attacks but thought to compromise to the least "Privilege escalation". The Security flaw... A user (victim) created a YT Community post, later an attacker while being an Admin of the same Channel has saved the HTTP Request that deletes a Community Post / Poll, then the attacker can replay that HTTP Request after he's demoted from Admin to Subtitle Editor that would delete the Post / Poll. I exploited this flaw I tried after 15 ...

Facebook Bug Bounty $$$$ : Crossposting Live Videos | Facebook Live

In the Facebook Page Settings, you could setup the option for Crossposting Live videos from other pages. The Attacker's page adds a Page (Victim's Page) for crossposting their videos Victim Page's Admin accepts the approval and the default option is Crossposting videos without further approval The Attacker starts live video and selects Victim's Page in the "Crosspost to more pages" Victim visits the Crossposting page in the Page settings and and removes Attacker's Page Attacker selects "Use camera" and clicks on "Go Live". The Victim's Page starts automatically crossposting the live video of Attacker, Bug Bounty of $500

Google form setting Bypass - Making my way to the Google's Hall of Fame !

G o o g l e ! Bug : Circumventing "Limit to 1 response" of Google forms ( Parameter Injection ) Discovered on: 30th, November 2016. Research Time: 2:00 p.m to 9:30 p.m. Earn more by display ads on blog with Lithific Ads The setting is "Limit to 1 response" which means only one response per user. Once you filled the form there will be no chance to edit the responses or again fill a new form. If you open the form to fill again, the response would be like the image below. There is no way to edit or fill another form (Hurdle 1). I created a test form and checked "Edit after submit". Once this test form is filled I can change the previous response. I clicked on the "Edit your response"and intercepted the request. I changed the form id and forwarded the request. I was able to see the form that was submitted. When I edited the form and submitted, a blank form ...

Yaswanth Mangalagiri

Search This Blog