Exécuter une analyse statique (SAST) sur le code source à la recherche du motif non sécurisé dans le flux de données.
CWE-346 Classe Brouillon
Origin Validation Error
This vulnerability occurs when an application fails to properly confirm the true origin of incoming data or communication, allowing attackers to spoof their source.
Définition
What is CWE-346?
This vulnerability occurs when an application fails to properly confirm the true origin of incoming data or communication, allowing attackers to spoof their source.
Origin Validation Errors happen because applications often trust metadata like IP addresses, DNS names, or HTTP headers that can be easily forged. Attackers exploit this by impersonating legitimate systems, tricking the application into accepting malicious data as if it came from a trusted source. This is a fundamental flaw in the trust boundary of the system.
To prevent this, developers must implement robust verification mechanisms that rely on unforgeable credentials, such as cryptographic signatures or secure tokens, rather than easily spoofed information. Always validate the origin at the point of trust establishment and consistently enforce this check for all subsequent interactions.
Impact réel
Real-world CVEs caused by CWE-346
-
DNS server can accept DNS updates from hosts that it did not query, leading to cache poisoning
-
Browser does not set Mark-of-the-Web (MotW) for a downloaded .EXE file if the name is close to the maximum path length, preventing recording of a zone identifier in the filename
-
Zip file extraction program does not propagate Mark-of-the-Web (MotW) metadata to files that are extracted from an Internet-downloaded Zip file
-
Zip file extraction program does not propagate Mark-of-the-Web (MotW) metadata to files that are extracted from an Internet-downloaded Zip file
-
DNS server can accept DNS updates from hosts that it did not query, leading to cache poisoning
-
DNS server caches glue records received from non-delegated name servers
-
user ID obtained from untrusted source (URL)
-
LDAP service does not verify if a particular attribute was set by the LDAP server
Comment les attaquants l'exploitent
Parcours de l'attaquant étape par étape
- 1
This Android application will remove a user account when it receives an intent to do so:
- 2
This application does not check the origin of the intent, thus allowing any malicious application to remove a user. Always check the origin of an intent, or create an allowlist of trusted applications using the manifest.xml file.
- 3
These Android and iOS applications intercept URL loading within a WebView and perform special actions if a particular URL scheme is used, thus allowing the Javascript within the WebView to communicate with the application:
- 4
A call into native code can then be initiated by passing parameters within the URL:
- 5
Because the application does not check the source, a malicious website loaded within this WebView has the same access to the API as a trusted site.
Exemple de code vulnérable
Vulnerable Java
This Android application will remove a user account when it receives an intent to do so:
IntentFilter filter = new IntentFilter("com.example.RemoveUser");
MyReceiver receiver = new MyReceiver();
registerReceiver(receiver, filter);
public class DeleteReceiver extends BroadcastReceiver {
@Override
public void onReceive(Context context, Intent intent) {
int userID = intent.getIntExtra("userID");
destroyUserData(userID);
}
} Charge utile de l'attaquant
A call into native code can then be initiated by passing parameters within the URL:
window.location = examplescheme://method?parameter=value Exemple de code sécurisé
Secure pseudo
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
const safe = validateAndEscape(input);
return executeWithGuards(safe);
} What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Liste de contrôle de prévention
How to prevent CWE-346
- Architecture Use safe-by-default frameworks and APIs that prevent the unsafe pattern from being expressible.
- Implementation Validate input at trust boundaries; use allowlists, not denylists.
- Implementation Apply the principle of least privilege to credentials, file paths, and runtime permissions.
- Testing Cover this weakness in CI: SAST rules + targeted unit tests for the data flow.
- Operation Monitor logs for the runtime signals listed in the next section.
Signaux de détection
How to detect CWE-346
Exécuter des tests de sécurité applicative dynamique (DAST) contre le point de terminaison en ligne.
Surveiller les journaux runtime pour détecter des traces d'exception inhabituelles, des entrées malformées ou des tentatives de contournement d'autorisation.
Revue de code : signaler tout nouveau code qui traite les entrées de cette surface sans utiliser les helpers du framework validés.
Plexicus détecte automatiquement CWE-346 et ouvre une PR de correction en moins de 60 secondes.
Codex Remedium analyse chaque commit, identifie cette faiblesse précise et livre une pull request prête à être relue avec le correctif. Pas de tickets. Pas de transferts.
Questions fréquentes Qu'est-ce que CWE-346 ?
Quelle est la gravité de CWE-346 ?
Quels langages ou plateformes sont affectés par CWE-346 ?
Comment puis-je prévenir CWE-346 ?
Comment Plexicus détecte et corrige CWE-346 ?
Où puis-je en savoir plus sur CWE-346 ?
Frequently asked questions
Qu'est-ce que CWE-346 ?
This vulnerability occurs when an application fails to properly confirm the true origin of incoming data or communication, allowing attackers to spoof their source.
Quelle est la gravité de CWE-346 ?
MITRE n'a pas publié de note de probabilité d'exploitation pour cette faiblesse. Traitez-la comme un impact moyen jusqu'à ce que votre modèle de menace prouve le contraire.
Quels langages ou plateformes sont affectés par CWE-346 ?
MITRE n'a pas spécifié les plateformes affectées pour ce CWE — il peut s'appliquer à la plupart des stacks applicatives.
Comment puis-je prévenir CWE-346 ?
Use safe-by-default frameworks, validate untrusted input at trust boundaries, and apply the principle of least privilege. Cover the data-flow signature in CI with SAST.
Comment Plexicus détecte et corrige CWE-346 ?
Le moteur SAST de Plexicus reconnaît la signature de flux de données de CWE-346 à chaque commit. Lorsqu'une correspondance est trouvée, notre agent Codex Remedium ouvre une PR de correction avec le code corrigé, les tests et un résumé d'une ligne pour le relecteur.
Où puis-je en savoir plus sur CWE-346 ?
MITRE publie la définition canonique à https://cwe.mitre.org/data/definitions/346.html. Vous pouvez également consulter la documentation OWASP et NIST pour des conseils adjacents.
Faiblesses associées
Weaknesses related to CWE-346
CWE-345 Parent
Insufficient Verification of Data Authenticity
This vulnerability occurs when an application fails to properly check where data comes from or confirm its legitimacy, allowing untrusted…
CWE-1293 Frère
Missing Source Correlation of Multiple Independent Data
This vulnerability occurs when a system trusts a single source of data without verification, making it impossible to detect if that source…
CWE-347 Frère
Improper Verification of Cryptographic Signature
This vulnerability occurs when an application fails to properly check the digital signature on data, or skips the verification step…
CWE-348 Frère
Use of Less Trusted Source
This vulnerability occurs when a system has access to multiple sources for the same critical data, but it chooses to rely on the less…
CWE-349 Frère
Acceptance of Extraneous Untrusted Data With Trusted Data
This vulnerability occurs when a system processes both trusted and untrusted data together, but fails to separate them. The application…
CWE-351 Frère
Insufficient Type Distinction
This vulnerability occurs when an application fails to properly differentiate between different types of data or objects, leading to…
CWE-352 Frère
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) happens when a web application cannot reliably tell if a user actually intended to submit a request,…
CWE-353 Frère
Missing Support for Integrity Check
This vulnerability occurs when a system uses a communication protocol that lacks built-in integrity verification, such as a checksum or…
CWE-354 Frère
Improper Validation of Integrity Check Value
This vulnerability occurs when software fails to properly check the integrity of data by validating its checksum or hash value. Without…
Prêt quand vous l'êtes
Arrêtez de payer par développeur.
Commencez à fermer la boucle.
Plexicus est l'ASPM natif IA qui scanne, filtre, corrige, penteste et explique — de façon autonome. Développeurs illimités, dépôts illimités, actions IA à usage équitable. Vrai niveau gratuit, €269/mo annuel quand vous êtes prêt.