IV84742: CSRF vulnerability where actions do not require a token

Some state-changing actions are not having the security token properly enforced, which can be a potential CSRF exposure. CSRF attacks with no token can generally be addressed by using the KNOWN_REFERRER_LIST property in the TRIRIGAWEB.properties file.

We added security validation to several pages throughout the platform. The issue has been resolved.

Continue reading


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s