Adding 'Weak Login Function' HTTP To HTTPS Variant about vulnerability-rating-taxonomy HOT 7 CLOSED

I would consider this to be the same as login over HTTP. Both require an active man in the middle, and i'd change both to P4 for that matter.

from vulnerability-rating-taxonomy.

I agree with @shpendk . This is same as login over HTTP and both should have the same priority.

from vulnerability-rating-taxonomy.

+1 for P4 for From HTTP to HTTPS

from vulnerability-rating-taxonomy.

I feel like the difference between these two is significant enough to warrant one priority point up in favor of Over HTTP variant. Let's consider the following:

• Sending credentials in clear text (Over HTTP) because of the nature of WIFI network traffic allows a simple eavesdropper to steal them. They literally fly in the air. Given how common WIFI networks are, this is a serious problem.
• Sending credentials from HTTP to HTTPS on the other hand requires a motivated attacker that is capable of establishing an active proxy, which lowers the risk.

from vulnerability-rating-taxonomy.

But is actively modifying a man in the middle connection that much harder than only eavesdropping? I would not think so.

from vulnerability-rating-taxonomy.

I also agree that both of these are similar. But, I would prioritize them both as P3 considering the easiness of executing such an attack.

from vulnerability-rating-taxonomy.

Looks like we won't be needing a new entry as the majority of us seem to agree that these variants pose the same risk. It's definitely great that we had this discussion, so we could shape our position. If anybody feels strongly that we should be downgrading the priority on the existing entry please feel free to make your case before we close this Issue.

from vulnerability-rating-taxonomy.