Security
Headlines
HeadlinesLatestCVEs

Headline

GHSA-5jcr-82fh-339v: Cross-Site-Scripting attack on `<RichTextField>`

Impact

All React applications built with react-admin and using the <RichTextField> are affected.

<RichTextField> outputs the field value using dangerouslySetInnerHTML without client-side sanitization. If the data isn’t sanitized server-side, this opens a possible Cross-Site-Scripting (XSS) attack.

Proof of concept:

import { RichTextField } from 'react-admin';

const record = {
    id: 1,
    body: `
<p>
<strong>War and Peace</strong> is a novel by the Russian author
<a href="https://en.wikipedia.org/wiki/Leo_Tolstoy" onclick="document.getElementById('stolendata').value='credentials';">Leo Tolstoy</a>,
published serially, then in its entirety in 1869.
</p>
<p onmouseover="document.getElementById('stolendata').value='credentials';">
It is regarded as one of Tolstoy's finest literary achievements and remains a classic of world literature.
</p>
<img src="x" onerror="document.getElementById('stolendata').value='credentials';" />
`,
};

const VulnerableRichTextField = () => (
    <>
        <RichTextField record={record} source="body" />
        <hr />
        <h4>Stolen data:</h4>
        <input id="stolendata" defaultValue="none" />
    </>
);

Patches

Versions 3.19.12 and 4.7.6 now use DOMPurify to escape the HTML before outputting it with React and dangerouslySetInnerHTML

Workarounds

You don’t need to upgrade if you already sanitize HTML data server-side.

Otherwise, you’ll have to replace the <RichTextField> by a custom field doing sanitization by hand:

// react-admin v4
import * as React from 'react';
import { memo } from 'react';
import PropTypes from 'prop-types';
import get from 'lodash/get';
import Typography from '@material-ui/core/Typography';
import { useRecordContext, sanitizeFieldRestProps, fieldPropTypes } from 'react-admin';
import purify from 'dompurify';

export const removeTags = (input) =>
    input ? input.replace(/<[^>]+>/gm, '') : '';

const RichTextField = memo(
    props => {
        const { className, emptyText, source, stripTags, ...rest } = props;
        const record = useRecordContext(props);
        const value = get(record, source);

        return (
            <Typography
                className={className}
                variant="body2"
                component="span"
                {...sanitizeFieldRestProps(rest)}
            >
                {value == null && emptyText ? (
                    emptyText
                ) : stripTags ? (
                    removeTags(value)
                ) : (
                    <span
                        dangerouslySetInnerHTML={{
                            __html: purify.sanitize(value),
                        }}
                    />
                )}
            </Typography>
        );
    }
);

RichTextField.defaultProps = {
    addLabel: true,
    stripTags: false,
};

RichTextField.propTypes = {
    // @ts-ignore
    ...Typography.propTypes,
    ...fieldPropTypes,
    stripTags: PropTypes.bool,
};

RichTextField.displayName = 'RichTextField';

export default RichTextField;

References

https://github.com/marmelab/react-admin/pull/8644, https://github.com/marmelab/react-admin/pull/8645

ghsa
#xss#vulnerability#nodejs#js#git#auth
  1. GitHub Advisory Database
  2. GitHub Reviewed
  3. CVE-2023-25572

Cross-Site-Scripting attack on `<RichTextField>`

Moderate severity GitHub Reviewed Published Feb 13, 2023 in marmelab/react-admin • Updated Feb 14, 2023

Package

npm ra-ui-materialui (npm)

Affected versions

>= 4.0.0, < 4.7.6

< 3.19.12

Patched versions

4.7.6

3.19.12

< 3.19.12

>= 4.0.0, < 4.7.6

Impact

All React applications built with react-admin and using the <RichTextField> are affected.

<RichTextField> outputs the field value using dangerouslySetInnerHTML without client-side sanitization. If the data isn’t sanitized server-side, this opens a possible Cross-Site-Scripting (XSS) attack.

Proof of concept:

import { RichTextField } from 'react-admin’;

const record = { id: 1, body: ` <p> <strong>War and Peace</strong> is a novel by the Russian author <a href="https://en.wikipedia.org/wiki/Leo_Tolstoy" onclick="document.getElementById(‘stolendata’).value=’credentials’;">Leo Tolstoy</a>, published serially, then in its entirety in 1869. </p> <p onmouseover="document.getElementById(‘stolendata’).value=’credentials’;"> It is regarded as one of Tolstoy’s finest literary achievements and remains a classic of world literature. </p> <img src="x" onerror="document.getElementById(‘stolendata’).value=’credentials’;" /> `, };

const VulnerableRichTextField = () => ( <> <RichTextField record={record} source="body" /> <hr /> <h4>Stolen data:</h4> <input id="stolendata" defaultValue="none" /> </> );

Patches

Versions 3.19.12 and 4.7.6 now use DOMPurify to escape the HTML before outputting it with React and dangerouslySetInnerHTML

Workarounds

You don’t need to upgrade if you already sanitize HTML data server-side.

Otherwise, you’ll have to replace the <RichTextField> by a custom field doing sanitization by hand:

// react-admin v4 import * as React from 'react’; import { memo } from 'react’; import PropTypes from 'prop-types’; import get from 'lodash/get’; import Typography from '@material-ui/core/Typography’; import { useRecordContext, sanitizeFieldRestProps, fieldPropTypes } from 'react-admin’; import purify from 'dompurify’;

export const removeTags = (input) => input ? input.replace(/<[^>]+>/gm, ‘’) : '’;

const RichTextField = memo( props => { const { className, emptyText, source, stripTags, …rest } = props; const record = useRecordContext(props); const value = get(record, source);

    return (
        <Typography
            className\={className}
            variant\="body2"
            component\="span"
            {...sanitizeFieldRestProps(rest)}
        \>
            {value \== null && emptyText ? (
                emptyText
            ) : stripTags ? (
                removeTags(value)
            ) : (
                <span
                    dangerouslySetInnerHTML\={{
                        \_\_html: purify.sanitize(value),
                    }}
                /\>
            )}
        </Typography\>
    );
}

);

RichTextField.defaultProps = { addLabel: true, stripTags: false, };

RichTextField.propTypes = { // @ts-ignore …Typography.propTypes, …fieldPropTypes, stripTags: PropTypes.bool, };

RichTextField.displayName = 'RichTextField’;

export default RichTextField;

References

marmelab/react-admin#8644, marmelab/react-admin#8645

References

  • GHSA-5jcr-82fh-339v
  • https://nvd.nist.gov/vuln/detail/CVE-2023-25572
  • marmelab/react-admin#8644
  • marmelab/react-admin#8645
  • https://github.com/marmelab/react-admin/releases/tag/v3.19.12
  • https://github.com/marmelab/react-admin/releases/tag/v4.7.6

Last updated

Feb 14, 2023

Published to the GitHub Advisory Database

Feb 14, 2023

Published by the National Vulnerability Database

Feb 13, 2023

Related news

CVE-2023-25572: Release 4.7.6 · marmelab/react-admin

react-admin is a frontend framework for building browser applications on top of REST/GraphQL APIs. react-admin prior to versions 3.19.12 and 4.7.6, along with ra-ui-materialui prior to 3.19.12 and 4.7.6, are vulnerable to cross-site scripting. All React applications built with react-admin and using the `<RichTextField>` are affected. `<RichTextField>` outputs the field value using `dangerouslySetInnerHTML` without client-side sanitization. If the data isn't sanitized server-side, this opens a possible cross-site scripting (XSS) attack. Versions 3.19.12 and 4.7.6 now use `DOMPurify` to escape the HTML before outputting it with React and `dangerouslySetInnerHTML`. Users who already sanitize HTML data server-side do not need to upgrade. As a workaround, users may replace the `<RichTextField>` by a custom field doing sanitization by hand.

ghsa: Latest News

GHSA-hqmp-g7ph-x543: TunnelVision - decloaking VPNs using DHCP