Fintech Security Scan Finds Exposed Tomcat Errors, WordPress XML-RPC Methods and SPF Misconfiguration
Summary
CloudSEK’s scan of a fintech firm’s public-facing assets found exposed Tomcat stack traces, WordPress XML-RPC methods and a misconfigured SPF record, which could aid reconnaissance and email spoofing. The article recommends limiting disclosures and unused features.
Key points
- The assessment identified publicly exposed Tomcat stack traces that could reveal application details to attackers.
- WordPress XML-RPC exposed system methods, potentially aiding reconnaissance or brute-force attempts.
- An insecure SPF configuration could enable email spoofing and phishing.
- The article recommends hiding detailed error messages, restricting unused externally accessible features, and reviewing email settings.
Article Details
- Topic
- Security assessment of a fintech firm's public-facing assets, identifying application error disclosures, exposed WordPress XML-RPC methods, and an insecure SPF configuration.
Vendors
Products
BeVigilCloudSEK’s BeVigil platform recently conducted an in-depth scan of a leading fintech company's public-facing assets and discovered multiple vulnerabilities that, if left unaddressed, could compromise data integrity,TomcatApplication Error Disclosure and Exploitation: With internal application details revealed through Tomcat stack traces, attackers can gain insights into the application's code structure, enabling more precise andWordPressRemote Method Enumeration and Abuse: Exposed system methods via WordPress XML-RPC allow attackers to enumerate available functions, increasing the risk of brute-force attacks or targeted reconnaissance.