Anypoint Best Practices

(14 reviews)

no-eval-in-markdown

general > no-eval-in-markdown


Guidance

This rule protects against cross-site scripting (XSS) attacks that could happen when you add description
documents from third parties and use the parsed content rendered in HTML/JS. If one of those third parties
does something like inject `eval()` JavaScript statements, it could lead to an XSS attack.

Message

Don not use `eval()` in markdown.

Examples

valid

#%RAML 1.0
title: ANG Governance xAPI
description: ANG Governance xAPI

invalid

#%RAML 1.0
title: ANG Governance xAPI
description: ANG Governance xAPI eval(...)

Applies to WebAPI

Constraint

Type: Declarative Validation

Reviews

TypeRuleset
OrganizationMuleSoft
Published by
MuleSoft Organization
Published onDec 11, 2023
Asset overview

Asset versions for 1.6.x

Asset versions
VersionActions
1.6.1
1.6.0

Tags