News for hackers. Stuff that matters.
Re:Is serverless insecure? Let's find out by benmanns on Saturday August 18, 2018 @06:03PM (#17791048)

  AWS_SESSION_TOKEN=FQoGZXIvYXdzEL7//////////wEaDLrjfq5THKULF+vCbyLdAXvIJIQYpbvyNbsoM78owNvdOi4xqqwm0kYRol0RLCtpO9QnBhn+4LhWWZHSjH0vfxRgbY3trqeTfX/U4c1zmtjMEbyN9ALic8Jo2s6m4CRdB+KMLdjg5/UKr1InaT2eONXqJ0JQYe712luic6sqbP5xlXa5QL2Z/+LoKJMs3PHgCOtjzUhPvLph5J+DDIb4I/xuaWwntrMtxXY7Ayo9YQGlh5zczJqhepBrig2Ajd7/eV0eelB/FxoQI493vItYtWnpGk5Cq4CAGH9a/XTDAD8+2Hui+r6PvdBYdbBlKN2J4tsF
  AWS_SECRET_ACCESS_KEY=IUsl7aO1EB5SNdlvivgNKjLwsLq6Mxj0vVX1bw5y
  AWS_ACCESS_KEY_ID=ASIARZMXIAFTOAUFCQFN
  $ aws sts get-caller-identity
  {
      "UserId": "AROAI55KPKEETYCGL4SXW:exec",
      "Account": "123260633446",
      "Arn": "arn:aws:sts::123260633446:assumed-role/lambda_basic_execution/exec"
  }
That's all I've gotten so far.
Re:Is serverless insecure? Let's find out by benmanns on Saturday August 18, 2018 @08:08PM (#17791657)
Found something! I'll post if/when the hole is closed. Til then it could cost some $$$.
Re:Is serverless insecure? Let's find out by jcims on Monday August 20, 2018 @07:42PM (#17805222)
can you share yet
Re:Is serverless insecure? Let's find out by partycoder on Saturday August 18, 2018 @10:31PM (#17792213)

    env | grep AWS
Would provide a similar output to the first part. Also:

    cat /proc/1/environ
Re:Is serverless insecure? Let's find out by neopallium on Saturday August 18, 2018 @11:15PM (#17792361)
Also with: ps get

Found that accidentally because of autocomplete on my phone changed "-ef" to "get".

Re:Is serverless insecure? Let's find out by partycoder on Sunday August 19, 2018 @03:59PM (#17795892)
"ps e" is usually enough to see the environment variables. g is similar to (if not equal to) a. t would display the tty information.