CAPEC-631: SoundSquatting
Also known as: Homophone Attack
An adversary registers a domain name that sounds the same as a trusted domain, but has a different spelling. A SoundSquatting attack takes advantage of a user's confusion of the two words to direct Internet traffic to adversary-controlled destinations. SoundSquatting does not require an attack against the trusted domain or complicated reverse engineering.
Last updated
Overview
CAPEC-631 (SoundSquatting) is a detailed-level attack pattern catalogued by MITRE in the Common Attack Pattern Enumeration and Classification (CAPEC). It describes a recurring method attackers use to exploit software weaknesses.
How the attack works
The phases an attacker typically follows to carry out this attack.
- Step 1Explore
[Determine target website] The adversary first determines which website to impersonate, generally one that is trusted, receives a consistent amount of traffic, and is a homophone.
- Research popular or high traffic websites which are also homophones.
- Step 2Experiment
[Impersonate trusted domain] In order to impersonate the trusted domain, the adversary needs to register the SoundSquatted URL.
- Register the SoundSquatted domain.
- Step 3Exploit
[Deceive user into visiting domain] Finally, the adversary needs to deceive a user into visiting the SoundSquatted domain.
- Execute a phishing attack and send a user an e-mail convincing the user to click on a link leading the user to the SoundSquatted domain.
- Assume that a user will unintentionally use the homophone in the URL, leading the user to the SoundSquatted domain.
What the attacker needs
Prerequisites
- An adversary requires knowledge of popular or high traffic domains, that could be used to deceive potential targets.
Skills required
- Low skill: Adversaries must be able to register DNS hostnames/URL’s.
Consequences
What a successful CAPEC-631 attack can achieve.
Other
Affects: Other
Depending on the intention of the adversary, a successful SoundSquatting attack can be leveraged to execute more complex attacks such as cross-site scripting or stealing account credentials.
How to mitigate it
Defenses that reduce the risk of CAPEC-631.
- Authenticate all servers and perform redundant checks when using DNS hostnames.
- Purchase potential SoundSquatted domains and forward to legitimate domain.
Examples
An adversary sends an email, impersonating the popular banking website guaranteebanking.com, to a user stating that they have just received a new deposit and to click the given link to confirm the deposit. However, the link the in email is guarantybanking.com instead of guaranteebanking.com, which the user clicks without fully reading the link. The user is directed to the adversary's website, which appears as if it is the legitimate guaranteebanking.com login page. The user thinks they are logging into their account, but have actually just given their guaranteebanking.com credentials to the adversary. The adversary can now use the user's legitimate guaranteebanking.com credentials to log into the user's account and steal any money which may be in the account. See also: SoundSquatting vulnerability allows an adversary to impersonate a trusted domain and leverages a user's confusion between the meaning of two words which are pronounced the same into visiting the malicious website to steal user credentials.
Terminology & mappings
Alternate terms
- Homophone Attack
Frequently asked questions
Common questions about CAPEC-631.
- What is CAPEC-631?
- An adversary registers a domain name that sounds the same as a trusted domain, but has a different spelling. A SoundSquatting attack takes advantage of a user's confusion of the two words to direct Internet traffic to adversary-controlled destinations. SoundSquatting does not require an attack against the trusted domain or complicated reverse engineering.
- How does a SoundSquatting attack work?
- It typically unfolds over 3 phases. It begins with: [Determine target website] The adversary first determines which website to impersonate, generally one that is trusted, receives a consistent amount of traffic, and is a homophone.
- How do you prevent CAPEC-631?
- Authenticate all servers and perform redundant checks when using DNS hostnames.
- How severe is CAPEC-631?
- MITRE rates CAPEC-631 as Medium severity with low likelihood of attack.
References
Attack-pattern data is sourced from the MITRE CAPEC catalog (v3.9). Weakness associations link to the corresponding CWE entries on RadicalNotion.AI.
Defend against CAPEC-631
Track the CVEs and weaknesses attackers exploit with this technique, with AI-written analysis and remediation guidance.