DEV Community

StarkMan
StarkMan

Posted on

Apache Tez UI Counts Are Small, but Application History and ACLs Still Matter

Apache Tez UI Counts Are Small, but Application History and ACLs Still Matter

Apache Tez is a data-processing framework used beneath other query and batch systems. Its UI can expose application history, directed acyclic graph information, counters, and diagnostic details. Small internet counts do not make those records harmless. They make ownership confirmation and scope review more practical.

What the measurement found

On 2026-11-19, a count-only ZoomEye SDK query used sub_type=all, page 1, and pagesize 1. app="Apache Tez" returned zero. title="Apache Tez" returned 2. title="Tez UI" returned 21.

The two title queries are not interchangeable. "Apache Tez" may identify a project page or product reference. "Tez UI" is closer to the application-history interface but can still match documentation or a dashboard that comments on Tez. Neither proves that a UI contains live data.

Review what the UI reveals

Apache Tez documentation describes ACL behavior and the relationship between application ACLs and the UI. A reviewer should identify which application records are visible, whether access requires authentication, and whether the UI trusts YARN or another upstream identity.

Application history can include table names, query text, file paths, container logs, counters, and failure diagnostics. These details may reveal data sources, business logic, and service accounts. A read-only interface can still be sensitive.

If the UI is backed by a timeline server or history service, review that upstream service too. The front end may enforce one policy while the history API remains reachable through another path. Check direct access to the application-timeline endpoints and any reverse-proxy exceptions.

Align ACLs with data sensitivity

Use a clear test matrix: application owner, authorized teammate, unrelated user, and unauthenticated visitor. Repeat it for an application that contains sensitive identifiers and one that is a harmless test. Confirm that the same rule is enforced for list, detail, logs, and counters.

Review the identity mapping between the UI and the cluster. A display name is not an authorization decision. If the UI derives access from YARN or a proxy header, confirm that untrusted clients cannot set or forge that header.

Verify deployment and retention

Record the UI host, port, base path, version, authentication layer, upstream history service, and data retention period. Determine whether old application records are still present after the source data or credentials have changed.

If the UI is small and internal, ensure that network policy prevents accidental public reachability. If the count is based on a public page, confirm whether it is a demo or documentation instance rather than a production cluster. Do not query application data or search for sensitive paths during discovery.

The small counts make a complete manual triage feasible. Compare all observed candidates with ownership records, then review confirmed UIs for application-level ACL and upstream API reach. The result should be a verified inventory of history surfaces, not a claim that 21 Tez UIs are exposed.

References

  • Apache Tez Tez UI, Apache Tez documentation. Retrieved 2026-11-18.
  • Access Control in Tez, Apache Tez documentation. Retrieved 2026-11-18.
  • TezConfiguration, Apache Tez API documentation. Retrieved 2026-11-18.
  • ZoomEye counts: app="Apache Tez" 0; title="Apache Tez" 2; title="Tez UI" 21. sub_type=all, page 1, pagesize 1, observed 2026-11-19 UTC+8.

Top comments (0)