Примеры использования Attacker could на Английском языке и их переводы на Русский язык
{-}
-
Colloquial
-
Official
An attacker could lock a post that was being edited.
On the other hand, such an attacker could counterfeit Zcash.
An attacker could just dump him, frightened of something.
If the GPS location was reported, the attacker could physically track the owner of the phone.
An attacker could lock a post that was being edited.
Люди также переводят
Thus, the"second channel" will not be able to save by RBS from theft of funds from his bank accounts because an attacker could read one-time passwords that come via SMS to a mobile device through an infected PC.
Which means the attacker could come and go without fear of being monitored.
An attacker could leverage this flaw to create or overwrite arbitrary files.
A remote unauthenticated attacker could leverage that to perform arbitrary code execution.
An attacker could provide a the malicious configuration file to trigger this vulnerability.
An unauthenticated remote attacker could exploit this flaw to execute arbitrary code with root privileges.
An attacker could provide a malicious configuration file to trigger this vulnerability.
A remote, authenticated attacker could cause the NFS server become deadlocked, resulting in a denial of service.
An attacker could execute arbitrary code via a TeX file with long picture, circle, input tags.
An unauthenticated remote attacker could take advantage of this flaw to execute arbitrary code as the web server user.
An attacker could use this flaw to cause graphviz to crash or possibly execute arbitrary code.
An attacker could exploit these vulnerabilities to overwrite arbitrary files or disclose system information.
An attacker could conduct a buffer overflow or buffer over-read attacks via a crafted GD file.
An attacker could use this flaw to cause graphviz to crash or possibly execute arbitrary code.
An attacker could craft ASN.1 data to forge RSA certificates with a valid certification chain to a trusted CA.
An attacker could exploit this and launch a denial-of-service attack by simultaneously requesting many large files.
An attacker could craft ASN.1 data to forge RSA certificates with a valid certification chain to a trusted CA.
An attacker could use those to cause a denial-of-service via out-of-bounds access or NULL pointer dereference.
An attacker could cause a memory corruption leading to a DoS(Denial of Service) with craft KDC or TIFF file.
An attacker could use crafted DNS records to crash the BIND server process, leading to a denial of service.
An attacker could use those to cause a denial-of-service via out-of-bounds access or NULL pointer dereference.
A non-authenticated remote attacker could mount a denial of service by submitting arbitrarily large passwords, tying up server resources in the expensive computation of the corresponding hashes to verify the password.
As a result, the attacker can bypass authentication.
Now an attacker can enumerate first letters.
Remote(authenticated) attackers could execute arbitrary commands as the web server user.