Logo
-

Byte Open Security

(ByteOS Network)

Log In

Sign Up

ByteOS

Security
Vulnerability Details
Registries
Custom Views
Weaknesses
Attack Patterns
Filters & Tools
CAPEC-89:Pharming
Attack Pattern ID:89
Version:v3.9
Attack Pattern Name:Pharming
Abstraction:Standard
Status:Draft
Likelihood of Attack:High
Typical Severity:Very High
DetailsContent HistoryRelated WeaknessesReports
▼Description
A pharming attack occurs when the victim is fooled into entering sensitive data into supposedly trusted locations, such as an online bank site or a trading platform. An attacker can impersonate these supposedly trusted sites and have the victim be directed to their site rather than the originally intended one. Pharming does not require script injection or clicking on malicious links for the attack to succeed.
▼Extended Description
▼Alternate Terms
▼Relationships
NatureTypeIDName
ChildOfM151Identity Spoofing
CanFollowS98Phishing
CanFollowD142DNS Cache Poisoning
CanFollowD543Counterfeit Websites
CanFollowD611BitSquatting
CanFollowD630TypoSquatting
CanFollowD631SoundSquatting
CanFollowD632Homograph Attack via Homoglyphs
Nature: ChildOf
Type: Meta
ID: 151
Name: Identity Spoofing
Nature: CanFollow
Type: Standard
ID: 98
Name: Phishing
Nature: CanFollow
Type: Detailed
ID: 142
Name: DNS Cache Poisoning
Nature: CanFollow
Type: Detailed
ID: 543
Name: Counterfeit Websites
Nature: CanFollow
Type: Detailed
ID: 611
Name: BitSquatting
Nature: CanFollow
Type: Detailed
ID: 630
Name: TypoSquatting
Nature: CanFollow
Type: Detailed
ID: 631
Name: SoundSquatting
Nature: CanFollow
Type: Detailed
ID: 632
Name: Homograph Attack via Homoglyphs
▼Execution Flow
Exploit
1.

Attacker sets up a system mocking the one trusted by the users. This is usually a website that requires or handles sensitive information.

Attacker sets up a system mocking the one trusted by the users. This is usually a website that requires or handles sensitive information.

Technique
2.

The attacker then poisons the resolver for the targeted site. This is achieved by poisoning the DNS server, or the local hosts file, that directs the user to the original website

The attacker then poisons the resolver for the targeted site. This is achieved by poisoning the DNS server, or the local hosts file, that directs the user to the original website

Technique
3.

When the victim requests the URL for the site, the poisoned records direct the victim to the attackers' system rather than the original one.

When the victim requests the URL for the site, the poisoned records direct the victim to the attackers' system rather than the original one.

Technique
4.

Because of the identical nature of the original site and the attacker controlled one, and the fact that the URL is still the original one, the victim trusts the website reached and the attacker can now "farm" sensitive information such as credentials or account numbers.

Because of the identical nature of the original site and the attacker controlled one, and the fact that the URL is still the original one, the victim trusts the website reached and the attacker can now "farm" sensitive information such as credentials or account numbers.

Technique
▼Prerequisites
Vulnerable DNS software or improperly protected hosts file or router that can be poisoned
A website that handles sensitive information but does not use a secure connection and a certificate that is valid is also prone to pharming
▼Skills Required
Medium

The attacker needs to be able to poison the resolver - DNS entries or local hosts file or router entry pointing to a trusted DNS server - in order to successfully carry out a pharming attack. Setting up a fake website, identical to the targeted one, does not require special skills.

▼Resources Required
None: No specialized resources are required to execute this type of attack. Having knowledge of the way the target site has been structured, in order to create a fake version, is required. Poisoning the resolver requires knowledge of a vulnerability that can be exploited.
▼Indicators
▼Consequences
ScopeLikelihoodImpactNote
ConfidentialityN/ARead DataN/A
Scope: Confidentiality
Likelihood: N/A
Impact: Read Data
Note: N/A
▼Mitigations
All sensitive information must be handled over a secure connection.
Known vulnerabilities in DNS or router software or in operating systems must be patched as soon as a fix has been released and tested.
End users must ensure that they provide sensitive information only to websites that they trust, over a secure connection with a valid certificate issued by a well-known certificate authority.
▼Example Instances
▼Related Weaknesses
IDName
CWE-346Origin Validation Error
CWE-350Reliance on Reverse DNS Resolution for a Security-Critical Action
ID: CWE-346
Name: Origin Validation Error
ID: CWE-350
Name: Reliance on Reverse DNS Resolution for a Security-Critical Action
▼Taxonomy Mappings
Taxonomy NameEntry IDEntry Name
▼Notes
▼References
Details not found