Rest tampered request t uri= - Common causes and quick fixes

Rest tampered request t uri= – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-6.8

Briefly, this error occurs when the Elasticsearch REST API receives a request that has been tampered with or malformed. This could be due to incorrect syntax, invalid parameters, or unauthorized modifications. To resolve this issue, you should first verify the syntax and parameters of your request. Ensure that it adheres to the correct format and includes all necessary information. If the problem persists, check for any unauthorized access or modifications to your request. Implementing proper access controls and security measures can help prevent such issues.

This guide will help you check for common problems that cause the log ” {}[rest] [tampered_request]\t{}; uri=[{}]{} ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “{}[rest] [tampered_request]\t{}; uri=[{}]{}” classname is DeprecatedLoggingAuditTrail.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        if (events.contains(TAMPERED_REQUEST) && (eventFilterPolicyRegistry.ignorePredicate().test(AuditEventMetaInfo.EMPTY) == false)) {
            if (includeRequestBody) {
                logger.info("{}[rest] [tampered_request]\t{}; uri=[{}]{}; request_body=[{}]"; localNodeInfo.prefix; hostAttributes(request);
                        request.uri(); opaqueId(); restRequestContent(request));
            } else {
                logger.info("{}[rest] [tampered_request]\t{}; uri=[{}]{}"; localNodeInfo.prefix; hostAttributes(request); request.uri();
                        opaqueId());
            }
        }
    }