all 2 comments

sorted by: hot top controversial new old
[–] 2 points 7 months ago (1 child)

The researchers found 1,748 active, verified credentials from major service providers (including Amazon Web Services, Stripe and OpenAI). These credentials were found publicly accessible within the live code of websites.

I mean, what else is new?

  • source
  • hideshow 1 child comment
  • 3 comments in c/cybersecurity@sh.itjust.works view that post
    [–] 7 points 7 months ago (1 child)

    Remember when writing a client side JavaScript application all that code is transferred to the client machine and executed. Don't put any sensitive code or strings in that code.

  • source
  • hideshow 1 child comment
  • [–] 5 points 7 months ago

    Yep. Use free tools like gitguardian, gitleaks, etc. and run them in pre-commit hooks. Makes it a lot easier to catch.

    And if you leak one by accident, change it immediately. There are bots trolling sites and repos for this information.

  • source
  • parent
  • [–] 6 points 7 months ago

    Sigh. Don't hardcode credentials in scripts, especially client-facing ones! If you must have credentials in plaintext on a file system, at least do something like PostgreSQL's pgpass file (and don't commit it to your version control system, or have it accessible via your web server!) with the appropriate user permissions set on it.

  • source
  • 1 comment in c/cybersecurity@infosec.pub view that post
    [–] 4 points 7 months ago

    The researchers found 1,748 active, verified credentials from major service providers (including Amazon Web Services, Stripe and OpenAI). These credentials were found publicly accessible within the live code of websites.

    I mean, what else is new?

  • source