TypeError: decodeComponents(...).join is not a function
See original GitHub issueVersion: v7.1.1
Crash occured when # kun%ea%ba%5a%ba
is parsed by queryString.parse
This hash is valid and should be parsed correctly as { ' kun%ea%ba%5a%ba': null }
For example in chrome’s development tools’ console the url https://google.com# kun%ea%ba%5a%ba
can be parsed without problems:
const url = new URL("https://google.com# kun%ea%ba%5a%ba");
url
Code to reproduce
const queryString = require('query-string');
const parsed = queryString.parse("# kun%ea%ba%5a%ba");
console.log(parsed);
Results
TypeError: decodeComponents(...).join is not a function
Issue Analytics
- State:
- Created a year ago
- Comments:12 (4 by maintainers)
Top Results From Across the Web
TypeError: join is not a function in JavaScript | bobbyhadz
The "TypeError join is not a function" occurs when we call the `join()` method on a value that is not an array. To...
Read more >Join is not a function - Stack Overflow
join () is an array-function, you cannot use it on a string: https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Array/join.
Read more >gatsby - UNPKG
__esModule = true;","function _nonIterableRest() {\n throw new TypeError(\"Invalid attempt to destructure non-iterable instance.\\nIn order to be iterable, ...
Read more >decode-uri-component <=0.2.0 存在输入验证不当漏洞
... 字符(如“% ea% ba%5a% ba”)时会触发异常“Uncaught TypeError TypeError: decodeComponents (...).join is not a function”,使得服务停止响应。
Read more >decode-uri-component <=0.2.0 存在输入验证不当漏洞
... 类解析特制字符(如“%ea%ba%5a%ba”)时会触发异常“Uncaught TypeError TypeError: decodeComponents(...).join is not a function”,使得服务停止响应。
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ll try to get a release out today.
People see to be very friendly nowadays. Piling up my Twitter DMs because Snyk seems to mark this as high severity…
my advice is to ditch the vulnerable library. The issue was identified on the project in August and hasn’t been fixed yet. The project hasn’t had any meaningful activity on it in 3 years. Either fork and fix and use the forked repo or migrate away from it. We are seeing this as well, too.