CWE-1078 Class Incomplete

Inappropriate Source Code Style or Formatting

This weakness occurs when source code violates established style guidelines for formatting, indentation, whitespace, or commenting, making it difficult to read and maintain.

Definition

What is CWE-1078?

This weakness occurs when source code violates established style guidelines for formatting, indentation, whitespace, or commenting, making it difficult to read and maintain.
While inconsistent formatting doesn't directly cause security vulnerabilities, it creates a breeding ground for them. Poorly structured code is harder to review, making subtle logic flaws, missing security checks, or unintended behaviors much easier to miss during manual inspection or automated analysis. This readability deficit directly undermines the team's ability to identify and fix critical security issues before deployment. Addressing this requires integrating automated style checkers and formatters into the development workflow. Tools like linters and code formatters enforce consistency automatically, ensuring the codebase remains clean and reviewable. This proactive practice reduces cognitive load for developers, accelerates code reviews, and significantly improves the team's overall capacity to spot and remediate genuine security defects hidden within complex logic.
Real-world impact

Real-world CVEs caused by CWE-1078

No public CVE references are linked to this CWE in MITRE's catalog yet.

How attackers exploit it

Step-by-step attacker path

  1. 1

    The usage of symbolic names instead of hard-coded constants is preferred.

  2. 2

    The following is an example of using a hard-coded constant instead of a symbolic name.

  3. 3

    If the buffer value needs to be changed, then it has to be altered in more than one place. If the developer forgets or does not find all occurrences, in this example it could lead to a buffer overflow.

  4. 4

    In this example the developer will only need to change one value and all references to the buffer size are updated, as a symbolic name is used instead of a hard-coded constant.

Vulnerable code example

Vulnerable C

The following is an example of using a hard-coded constant instead of a symbolic name.

Vulnerable C 
char buffer[1024];
  ...
  fgets(buffer, 1024, stdin);
Secure code example

Secure C

If the buffer value needs to be changed, then it has to be altered in more than one place. If the developer forgets or does not find all occurrences, in this example it could lead to a buffer overflow.

Secure C 
enum { MAX_BUFFER_SIZE = 1024 };
  ...
  char buffer[MAX_BUFFER_SIZE];
  ...
  fgets(buffer, MAX_BUFFER_SIZE, stdin);
What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Prevention checklist

How to prevent CWE-1078

  • 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.
Detection signals

How to detect CWE-1078

SAST High

Run static analysis (SAST) on the codebase looking for the unsafe pattern in the data flow.

DAST Moderate

Run dynamic application security testing against the live endpoint.

Runtime Moderate

Watch runtime logs for unusual exception traces, malformed input, or authorization bypass attempts.

Code review Moderate

Code review: flag any new code that handles input from this surface without using the validated framework helpers.

Plexicus auto-fix

Plexicus auto-detects CWE-1078 and opens a fix PR in under 60 seconds.

Codex Remedium scans every commit, identifies this exact weakness, and ships a reviewer-ready pull request with the patch. No tickets. No hand-offs.

Get a demo Try Plexicus free
Frequently asked questions

Frequently asked questions

What is CWE-1078?

This weakness occurs when source code violates established style guidelines for formatting, indentation, whitespace, or commenting, making it difficult to read and maintain.

How serious is CWE-1078?

MITRE has not published a likelihood-of-exploit rating for this weakness. Treat it as medium-impact until your threat model proves otherwise.

What languages or platforms are affected by CWE-1078?

MITRE has not specified affected platforms for this CWE — it can apply across most application stacks.

How can I prevent CWE-1078?

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.

How does Plexicus detect and fix CWE-1078?

Plexicus's SAST engine matches the data-flow signature for CWE-1078 on every commit. When a match is found, our Codex Remedium agent opens a fix PR with the corrected code, tests, and a one-line summary for the reviewer.

Where can I learn more about CWE-1078?

MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/1078.html. You can also reference OWASP and NIST documentation for adjacent guidance.

Related weaknesses

Weaknesses related to CWE-1078

CWE-1076 Parent

Insufficient Adherence to Expected Conventions

This weakness occurs when software code, design, documentation, or other components fail to follow established industry or…

CWE-1045 Sibling

Parent Class with a Virtual Destructor and a Child Class without a Virtual Destructor

This occurs when a base class defines a virtual destructor, but a derived class inherits from it without declaring its own virtual…

CWE-1070 Sibling

Serializable Data Element Containing non-Serializable Item Elements

This weakness occurs when a class or data structure is marked as serializable, but it contains one or more member elements that cannot be…

CWE-1079 Sibling

Parent Class without Virtual Destructor Method

This occurs when a base class, designed to be inherited from, does not declare its destructor as virtual. This oversight prevents proper…

CWE-1082 Sibling

Class Instance Self Destruction Control Element

This vulnerability occurs when an object's code contains logic that triggers its own deletion or destruction during runtime.

CWE-1087 Sibling

Class with Virtual Method without a Virtual Destructor

This occurs when a class defines a virtual method but does not also provide a virtual destructor.

CWE-1091 Sibling

Use of Object without Invoking Destructor Method

This weakness occurs when a program accesses an object but fails to properly call its destructor or finalizer method. This leaves the…

CWE-1097 Sibling

Persistent Storable Data Element without Associated Comparison Control Element

This weakness occurs when a persistent data object lacks the necessary methods to be properly compared, which can lead to inconsistent or…

CWE-1098 Sibling

Data Element containing Pointer Item without Proper Copy Control Element

This weakness occurs when a data structure contains a pointer, but the code lacks proper methods to copy or initialize that pointer safely.

Resources

Further reading

Ready when you are

Don't Let Security
Weigh You Down.

Stop choosing between AI velocity and security debt. Plexicus is the only platform that runs Vibe Coding Security and ASPM in parallel — one workflow, every codebase.

Get started free Book a demo