Skip to content
← Back to activity

Immutable solution version

Bearer detects CWE-693 even after disabling x-powered-by header

Version 2Sign in to save

Complete solution

Shows how to fix bearer detects CWE-693 even after disabling x-powered-by header. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

What works: Bearer's javascriptexpressreduce_fingerprint rule flags CWE-693 even after you disable the x-powered-by header: the maintainer reproduced it and confirmed it's a bug in the rule itself. Until it's fixed, skipping that rule is the recommended workaround.

Steps

  1. What was reported:

Issue Bearer/bearer#1114 (closed, 9 comments): [!--- Provide a general summary of the issue in the Title above --] ## Description & Reproduction Upon running the below command for a node.js project


2. bearer detects `HIGH: Security misconfiguration detected. [CWE-693]` vulnerability. [image] After using [this](https://docs.bearer.com/reference/rules/javascript_express_reduce_fingerprint) and [this](https://stackoverflow.com/questions/10717685/how-to-remove-x-powered-by-in-expressjs) article as reference, I have tried both the below mentioned approaches. ## Approach 1: disabling the header ```javascript app.

3. What works:
Bearer's javascript_express_reduce_fingerprint rule flags CWE-693 even after you disable the x-powered-by header: the maintainer reproduced it and confirmed it's a bug in the rule itself. Until it's fixed, skipping that rule is the recommended workaround. If Bearer flags a misconfiguration you've already remediated, check whether the rule itself is at fault before changing more code.

## When to use

You are seeing this: If Bearer flags a misconfiguration you've already remediated, check whether the rule itself is at fault before changing more code. Use this skill when you run into "Bearer detects CWE-693 even after disabling x-powered-by header".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

## Sources

- https://docs.bearer.com/reference/rules/javascript_express_reduce_fingerprint

- https://stackoverflow.com/questions/10717685/how-to-remove-x-powered-by-in-expressjs

Evidence

In the GitHub issue, the reporter asked: Bearer detects CWE-693 even after disabling x-powered-by header. The working answer that came out of the thread: Bearer's javascriptexpressreduce_fingerprint rule flags CWE-693 even after you disable the x-powered-by header: the maintainer reproduced it and confirmed it's a bug in the rule itself. Until it's fixed, skipping that rule is the recommended workaround. If Bearer flags a misconfiguration you've already remediated, check whether the rule itself is at fault before changing more code. Source: https://github.com/Bearer/bearer/issues/1114

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_Af8JI2fC7Y_YomJVV77fKg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Bearer detects CWE-693 even after disabling x-powered-by header <span>— Vectle</span></a>