Page History

In Java, data is stored in big-endian format (also called network order). That is, all data is represented sequentially starting from the most significant bit (MSB) to the least significant. Prior JDK versions prior to JDK 1.4 , required definition of custom methods had to be defined to be compatible that manage reversing byte order to maintain compatibility with little-endian systems that use the reverse byte order. Handling byte order related . Correct handling of byte order–related issues is critical when exchanging data is to be exchanged in a networked environment that consists of machines varying in endiannessincludes both big-endian and little-endian machines or when working with other languages using Java Native Interface (JNI). Failure to handle data byte-ordering issues can cause misinterpretations and unexpected program behavior.

Noncompliant Code Example

The class java.io.DataInputStream defines read methods (readByte(), readShort(), readInt(), readLong(), readFloat(), and readDouble()) and the corresponding write methods . All these methods work with defined by class java.io.DataInputStream and class java.io.DataOutputStream operate only on big-endian data only. The use Use of these methods can be unsafe while interfacing interoperating with traditional languages, such as C or and C++, that do not provide is insecure because such languages lack any guarantees on about endianness. This noncompliant code example shows such a discrepancy. :

try {
  DataInputStream dis = null;
  try {
    dis = new DataInputStream(
  new FileInputStream("data"));
    // Little-endian data might be read as big-endian
    int serialNumber = dis.readInt();
  } catch (IOException x) {
    // Handle error
  } finally {
    if (dis != null) {
      try {
       dis.close();
      } catch (IOException e) {
      // Handle error
      }
    }
  }
}

Compliant Solution (ByteBuffer)

This compliant solution uses methods provided by class ByteBuffer [API 2014] to correctly extract an int from the original input value. It wraps the input byte array containing the integer bytes read-in into with a ByteBuffer and , sets the byte order to little-endian, and extracts the int. The result is stored in the integer serialNumber. Class ByteBuffer provides analogous get and put methods for other numeric types.

	try {
  DataInputStream dis = null;
  try {
    dis = new DataInputStream(
  new FileInputStream("data"));

    byte[] buffer = new byte[4];
    int bytesRead = dis.read(buffer);  // Bytes are read into buffer
    if (bytesRead != 4) {
      throw new IOException("Unexpected End of Stream");
    }
    int serialNumber = 
        ByteBuffer.wrap(buffer).order(ByteOrder.LITTLE_ENDIAN).getInt();
  } finally {
    if (dis != null) {
  try {
    dis.close();
  } catch (IOException x) {
    // Handle error
  }
    }
  }
} catch (IOException x) {
  // Handle error
}

Compliant Solution

...

(Define Special-Purpose Methods)

An alternative compliant solution is to define Assuming that an integer value is to be read from the file, read and write methods can be defined for handling little-endian data. The that support the necessary byte-swapping while reading from or writing to the file. In this example, the readLittleEndianInteger() method reads data four bytes into a byte buffer and then pieces together the integer in the right correct order. The writeLittleEndianInteger() method obtains bytes by repeatedly casting the integer so that the most least significant byte is extracted on successive right shifts. Long values can be handled by defining a byte buffer of size eight8.

	 
// readRead method
public static int readLittleEndianInteger(InputStream ips)
                                          throws IOException {
  byte[] buffer = new byte[4];
  int check = ips.read(buffer);

  if (check != 4) {
    throw new IOException("Unexpected End of Stream");
  }
 
  int result = (buffer[3] << 24) | (buffer[2] << 16) |
               (buffer[1] << 8)  | buffer[0];
  return result;
}

// writeWrite method
public static void writeLittleEndianInteger(int i, OutputStream ops)
  throws IOException {
  byte[] buffer = new byte[4];
  buffer[0] = (byte) i;
  buffer[1] = (byte) (i >> 8);
  buffer[2] = (byte) (i >> 16);
  buffer[3] = (byte) (i >> 24);
  ops.write(buffer);
}

Compliant Solution

...

(reverseBytes())

When programming for In JDK 1.5 +and later, use the reverseBytes() method defined in the classes Character, Short, Integer, and Long can be used to reverse the order of the bytes constituting the integerintegral value's bytes. Note that there is no such method for float and double valuesclasses Float and Double lack such a method.

	 
public static int reverse(int i) {
  return Integer.reverseBytes(i);
}

Risk Assessment

Reading and writing data without considering endianness may can lead to serious misinterpretations about of both the magnitude and sign , alikeof the data.

Automated Detection

TODO

Related Vulnerabilities

Search for vulnerabilities resulting from the violation of this rule on the CERT website.

References

\[[API 2006|AA. Java References#API 06]\] Class ByteBuffer: Methods {{wrap}} and {{order}}. Class Integer: method {{reverseBytes}}
\[[Harold 1997|AA. Java References#Harold 97]\] Chapter 2: Primitive Data Types, Cross Platform issues
\[[MITRE 2009|AA. Java References#MITRE 09]\] [CWE ID 198|http://cwe.mitre.org/data/definitions/198.html] "Use of Incorrect Byte Ordering"

Automated detection is infeasible in the general case.

Related Guidelines

Bibliography

...

Image Added Image Added Image AddedINT06-J. Do not use bitwise operators on integers incorrectly      06. Integers (INT)      INT08-J. Provide mechanisms to handle unsigned data when required