Skip to content
This repository was archived by the owner on Aug 29, 2018. It is now read-only.

Insecure Defaults Allow MITM Over TLS #22

Closed
cloudlena opened this issue Apr 29, 2016 · 2 comments
Closed

Insecure Defaults Allow MITM Over TLS #22

cloudlena opened this issue Apr 29, 2016 · 2 comments

Comments

@cloudlena
Copy link

Running nsp check using NSP's command line tool returns the following vulnerability:

┌───────────────┬───────────────────────────────────────────────────────┐
│               │ Insecure Defaults Allow MITM Over TLS                 │
├───────────────┼───────────────────────────────────────────────────────┤
│ Name          │ engine.io-client                                      │
├───────────────┼───────────────────────────────────────────────────────┤
│ Installed     │ 1.6.8                                                 │
├───────────────┼───────────────────────────────────────────────────────┤
│ Vulnerable    │ <= 99.999.99999 || <= 1.6.8                           │
├───────────────┼───────────────────────────────────────────────────────┤
│ Patched       │ None                                                  │
├───────────────┼───────────────────────────────────────────────────────┤
│ Path          │ feathers-socketio@1.4.0 > socket.io@1.4.5 > socket.i… │
├───────────────┼───────────────────────────────────────────────────────┤
│ More Info     │ https://nodesecurity.io/advisories/99                 │
└───────────────┴───────────────────────────────────────────────────────┘

There is no fix yet but we should include the fix as soon as it's released by engine.io-client.

@daffl
Copy link
Member

daffl commented Apr 29, 2016

I don't think there is much we can do. Looks like it'll be a patch release so we won't need to change any of the dependencies. I don't know why Socket.io releases take so long. The React Native fix also has been merged almost a month ago and all that needs to be done is a patch release that we're still waiting for.

@daffl
Copy link
Member

daffl commented May 7, 2016

It looks like this has been fixed now via socketio/engine.io-client@2a7a011

@daffl daffl closed this as completed May 7, 2016
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants