PCI v3.2-6.5.6
CAPEC-37
CWE-200
ISO27001-A.8.2.1
WASC-WASC-13
OWASP 2013-A6
OWASP 2017-A3
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

Sensitive Data Exposure - Twitter Access Token Secret

Severity:
Medium
Summary

Invicti detected various secrets such as API keys, database credentials, and/or cryptographic secrets. These secrets should be kept secret for security, but sometimes JavaScript files, error messages, etc. are leaked through.

Impact

Depending on the leaked secret, an attacker can perform one of the following types of attacks successfully:

  • Bypass Authorization
  • Unauthorized Access
  • Credentials Leakage
Remediation

It is recommended to revoke leaked secrets. Investigate and resolve the source of the leak. Hard-coded Secrets can be accidentally released to the public. Don't store these secrets on the application tree. Find the source of the leak and make sure it's disabled.

Required Skills for Successful Exploitation
Actions To Take
Vulnerability Index

You can search and find all vulnerabilities

Select Vulnerability
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Featured resources

Blog

Strengthening enterprise application security: Invicti acquires Kondukto

Blog

Modern AppSec KPIs: Moving from scan counts to real risk reduction

Blog

Friends don’t let friends shift left: Shift smarter with DAST-first AppSec

Blog

Vibe talking: Dan Murphy on the promises, pitfalls, and insecurities of vibe coding

Blog

What lies ahead for CMS.

Blog

How to integrate CMS with other tools.

Blog

Improve user experience through CMS.

Blog

How CMS can benefit e-commerce.

Blog

Stay updated on CMS trends.

Blog

Tips for improving CMS performance.

Blog

Learn how to secure your CMS.

Blog

Explore the advantages of CMS.

Blog

A comprehensive guide to CMS.

Build your resistance to threats. And save hundreds of hours each month.