CWE-580 Variante Rascunho

clone() Method Without super.clone()

This vulnerability occurs when a class's clone() method creates a new object directly instead of calling super.clone().

Definição

What is CWE-580?

This vulnerability occurs when a class's clone() method creates a new object directly instead of calling super.clone().
In Java, the proper way to implement the clone() method is to always start with a call to super.clone(). This call travels up the inheritance chain to Object.clone(), which performs the essential bitwise copy that establishes the correct object type and internal structure. Skipping this step and instantiating the object manually (e.g., using 'new') breaks the inherited cloning contract. When a parent class fails to call super.clone(), any subclass that inherits and uses its clone() method will receive an object of the parent's type, not its own. This causes a ClassCastException when the returned object is cast to the subclass type, leading to runtime failures. Adhering to the super.clone() convention ensures the cloning mechanism works correctly throughout the entire class hierarchy.
Impacto no mundo real

Real-world CVEs caused by CWE-580

Ainda não há referências CVE públicas associadas a este CWE no catálogo da MITRE.

Como os atacantes a exploram

Trajeto do atacante passo a passo

  1. 1

    Identificar um caminho de código que trata input não confiável sem validação.

  2. 2

    Criar um payload que explora o comportamento inseguro — injeção, traversal, overflow ou abuso de lógica.

  3. 3

    Entregar o payload através de um pedido normal e observar a reação da aplicação.

  4. 4

    Iterar até que a resposta exponha dados, execute código do atacante ou escale privilégios.

Exemplo de código vulnerável

Vulnerable Java

The following two classes demonstrate a bug introduced by not calling super.clone(). Because of the way Kibitzer implements clone(), FancyKibitzer's clone method will return an object of type Kibitzer instead of FancyKibitzer.

Vulnerável Java 
public class Kibitzer {
  		public Object clone() throws CloneNotSupportedException {
  				Object returnMe = new Kibitzer();
  				...
  		}
  }
  public class FancyKibitzer extends Kibitzer{
  		public Object clone() throws CloneNotSupportedException {
  				Object returnMe = super.clone();
  				...
  		}
  }
Exemplo de código seguro

Secure pseudo

Seguro 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.
Lista de verificação de prevenção

How to prevent CWE-580

  • Implementation Call super.clone() within your clone() method, when obtaining a new object.
  • Implementation In some cases, you can eliminate the clone method altogether and use copy constructors.
Sinais de deteção

How to detect CWE-580

Automated Static Analysis High

Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)

Correção automática do Plexicus

O Plexicus deteta automaticamente o CWE-580 e abre um PR de correção em menos de 60 segundos.

O Codex Remedium analisa cada commit, identifica esta fraqueza exata e entrega um pull request pronto para revisão com o patch. Sem tickets. Sem transferências.

Obter uma demonstração Experimente o Plexicus gratuitamente
Perguntas frequentes

Frequently asked questions

O que é o CWE-580?

This vulnerability occurs when a class's clone() method creates a new object directly instead of calling super.clone().

Qual a gravidade do CWE-580?

A MITRE não publicou uma classificação de probabilidade de exploração para esta fraqueza. Trate-a como impacto médio até o seu modelo de ameaças provar o contrário.

Que linguagens ou plataformas são afetadas pelo CWE-580?

MITRE lists the following affected platforms: Java.

Como posso prevenir o CWE-580?

Call super.clone() within your clone() method, when obtaining a new object. In some cases, you can eliminate the clone method altogether and use copy constructors.

Como é que o Plexicus deteta e corrige o CWE-580?

O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-580 em cada commit. Quando é encontrada uma correspondência, o nosso agente Codex Remedium abre um PR de correção com o código corrigido, testes e um resumo de uma linha para o revisor.

Onde posso saber mais sobre o CWE-580?

A MITRE publica a definição canónica em https://cwe.mitre.org/data/definitions/580.html. Pode também consultar a documentação da OWASP e do NIST para orientações adjacentes.

Fraquezas relacionadas

Weaknesses related to CWE-580

CWE-664 Pai

Improper Control of a Resource Through its Lifetime

This vulnerability occurs when software fails to properly manage a resource throughout its entire lifecycle—from creation and active use…

CWE-118 Irmão

Incorrect Access of Indexable Resource ('Range Error')

This vulnerability occurs when software fails to properly check the boundaries of an indexed resource, like an array, buffer, or file,…

CWE-1229 Irmão

Creation of Emergent Resource

This vulnerability occurs when a system's normal operations unintentionally create new, exploitable resources that attackers can use to…

CWE-1250 Irmão

Improper Preservation of Consistency Between Independent Representations of Shared State

This vulnerability occurs when a system with multiple independent components (like distributed services or separate hardware units) each…

CWE-1329 Irmão

Reliance on Component That is Not Updateable

This vulnerability occurs when a product depends on a component that cannot be updated or patched to fix security flaws or critical bugs.

CWE-221 Irmão

Information Loss or Omission

This weakness occurs when an application fails to log critical security events or records them inaccurately, which can misguide security…

CWE-372 Irmão

Incomplete Internal State Distinction

This vulnerability occurs when an application fails to accurately track its own operational state. The system incorrectly assumes it's in…

CWE-400 Irmão

Uncontrolled Resource Consumption

This vulnerability occurs when an application fails to properly manage a finite resource, allowing an attacker to exhaust it and cause a…

CWE-404 Irmão

Improper Resource Shutdown or Release

This vulnerability occurs when a program fails to properly close or release a system resource—like a file handle, database connection, or…

Recursos

Further reading

Pronto quando você estiver

Pare de pagar por desenvolvedor.
Comece a fechar o ciclo.

O Plexicus é o ASPM nativo de IA que verifica, filtra, corrige, pentesta e explica — de forma autónoma. Programadores ilimitados, repos ilimitados, ações de IA de utilização justa. Nível gratuito real, €269/mo anual quando estiver pronto.

Começar grátis Reservar uma demo