# Credentials security vulnerability

**URL:** <https://discourse.nodered.org/t/credentials-security-vulnerability/90484>\
**Category:** General\
**Tags:** security\
**Created:** [27 August 2024 13:49 UTC](https://discourse.nodered.org/t/credentials-security-vulnerability/90484 "2024-08-27T13:49:21Z")\
**Posts on this page:** 5\
**Page:** 2

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [27 August 2024 16:42 UTC](https://discourse.nodered.org/t/credentials-security-vulnerability/90484/22 "2024-08-27T16:42:10Z")

</div>

> [@E1cid](#):
>
> You can access it, yes, it would be useless if you could not

It can be displayed in a debug node, and can be read from there.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [27 August 2024 17:01 UTC](https://discourse.nodered.org/t/credentials-security-vulnerability/90484/23 "2024-08-27T17:01:24Z")

</div>

> [@jbudd](#):
>
> it does not seem to reveal my $BankAccount credential flow variable.

I think that is because it isn't a real environment variable but rather a node-red construct. Where Node-RED allows you to access it using the same node-red mechanism.

`process.env` on the other hand does read the OS's environment variables out of system memory.

Though it probably only knows about the ones that existed when the current process started? Not sure, I haven't checked that but it would make sense.

---

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [27 August 2024 17:21 UTC](https://discourse.nodered.org/t/credentials-security-vulnerability/90484/24 "2024-08-27T17:21:28Z")

</div>

> [@E1cid](#):
>
> You can not export it in a flow

That is the key benefit of using an environment variable, of whatever type.

> [@E1cid](#):
>
> It can not be seen in the env config.

I suppose that's a _slight_ benefit, at least if you have read-only dashboard users who can't deploy flow changes.

---

<div class="post-metadata">

**Author:** ![E1cid](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/e1cid/32/77971_2.png) [@E1cid](https://discourse.nodered.org/u/E1cid)\
**Post date:** [27 August 2024 17:26 UTC](https://discourse.nodered.org/t/credentials-security-vulnerability/90484/26 "2024-08-27T17:26:23Z")

</div>

You are repeating what @jbudd said above.

@jbudd  
Anything can be read in editor here is my flows\_cred.json decrypted by node-red, I am not going to show how but anything can be hacked if you have access to the editor, node-red is a powerful tool.

 ![chrome_screenshot_27 Aug 2024 18_16_29 BST](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/8/7/87634a08db9ffb12b531c949c402a79a735d4258.png)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [25 November 2024 17:27 UTC](https://discourse.nodered.org/t/credentials-security-vulnerability/90484/27 "2024-11-25T17:27:17Z")

</div>

Closed on 25 November 2024 17:27 UTC

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

[Previous page](https://discourse.nodered.org/t/credentials-security-vulnerability/90484.md?page=1)
